TJaniF opened a new issue, #49861:
URL: https://github.com/apache/airflow/issues/49861
### Apache Airflow version
3.0.0
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
Breeze current main. I was testing a tutorial flow and ran into a dag bundle
not found error.
Repro steps:
1. `breeze down` for a clean slate
2. Set
```
AIRFLOW__DAG_PROCESSOR__DAG_BUNDLE_CONFIG_LIST='[
{
"name": "dags-folder1",
"classpath": "airflow.dag_processing.bundles.local.LocalDagBundle",
"kwargs": {}
}
]'
```
3. `breeze start-airflow --executor CeleryExecutor --backend postgres` and
run one dag.
4. `stop_airflow` but do not breeze down
5. change the dag bundle name
```
AIRFLOW__DAG_PROCESSOR__DAG_BUNDLE_CONFIG_LIST='[
{
"name": "dags-folder2",
"classpath": "airflow.dag_processing.bundles.local.LocalDagBundle",
"kwargs": {}
}
]'
```
6. `breeze start-airflow --executor CeleryExecutor --backend postgres`
See an error in the UI
The API-server crashes because it can't find the first bundle
In the db you can see both bundles exist, and the old one is correctly
marked `f` for the active column:
```
airflow=# select * from dag_bundle;
name | active | version | last_refreshed
--------------+--------+---------+-------------------------------
dags-folder | f | | 2025-04-28 07:00:31.281333+00
dags-folder2 | t | | 2025-04-28 07:01:22.986212+00
(2 rows)
airflow=#
```
### What you think should happen instead?
This used to work with the old bundle being ignored, only the currently
configured bundle counting.
### How to reproduce
See above.
### Operating System
MacOS
### Versions of Apache Airflow Providers
breeze soup
### Deployment
Other
### Deployment details
breeze main
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
