shivaam commented on issue #62246:
URL: https://github.com/apache/airflow/issues/62246#issuecomment-3982068060
Findings:
[Seems like a bug]
1. When using `dag_bundle_config_list` with `team_name` in multi-team mode,
the dag-processor's
`sync_bundles_to_db` method logs "Added new DAG bundle" for team-scoped
bundles but the records
are not persisted to the `dag_bundle` table. Non-team bundles (like
`shared_dags` and `example_dags`)
persist correctly. The dag-processor then continuously logs "Bundle model
not found" for the
team bundles, and their DAGs are never processed.
```
dag_bundle_config_list = [
{"name": "team_alpha_dags", "classpath":
"airflow.providers.amazon.aws.bundles.s3.S3DagBundle", "kwargs":
{"bucket_name": "airflow-ecs-dags-ACCOUNT-REGION", "prefix": "team_alpha"},
"team_name": "team_alpha"},
{"name": "team_beta_dags", "classpath":
"airflow.providers.amazon.aws.bundles.s3.S3DagBundle", "kwargs":
{"bucket_name": "airflow-ecs-dags-ACCOUNT-REGION", "prefix": "team_beta"},
"team_name": "team_beta"},
{"name": "shared_dags", "classpath":
"airflow.providers.amazon.aws.bundles.s3.S3DagBundle", "kwargs":
{"bucket_name": "airflow-ecs-dags-ACCOUNT-REGION", "prefix": "shared"}}
]
```
2. If multi team config in the executor is not set it throws an error. My
scheduler config has multi_team=True though.
```
what is the last log
{"timestamp":"2026-03-02T04:34:49.374043Z","level":"error","event":"Top level
error","logger":"task","filename":"task_runner.py","lineno":1827,"error_detail":[{"exc_type":"AirflowConfigException","exc_value":"Section
`dag_processor` key `dag_bundle_config_list` cannot have a team name when
multi-team mode is disabled.
To enable multi-team, you need to update section `core` key `multi_team` in
your
config.","exc_notes":[],"syntax_error":null,"is_cause":false,"frames":[{"filename":"/opt/airflow/task-sdk/src/airflow/sdk/execution_time/task_runner.py","lineno":1806,"name":"main"},{"filename":"/opt/airflow/task-s
is that the start
```
--
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]
