SkanderD1999 commented on issue #67271: URL: https://github.com/apache/airflow/issues/67271#issuecomment-4518313868
I was able to partially reproduce this issue in a Docker Compose environment. Environment: * Apache Airflow version: 3.2.1 * Deployment: Docker Compose * Operating System: Docker Desktop on Windows * Database: PostgreSQL Steps followed: 1. Configured a local DAG bundle named `ex_dag_bundle` using `LocalDagBundle`. 2. Added a minimal DAG named `bundle_bug_test` inside the bundle directory. 3. Started Airflow and confirmed that the DAG was listed with `bundle_name = ex_dag_bundle`. 4. Removed the bundle from `dag_bundle_config_list`. 5. Restarted Airflow. 6. Checked the DAG processor logs and database state. Observed result: The DAG processor logs indicate that the bundle was disabled: ```text DAG bundle ex_dag_bundle is no longer found in config and has been disabled ``` Database results after removing the bundle: ```sql SELECT name, active FROM dag_bundle WHERE name = 'ex_dag_bundle'; -- ex_dag_bundle | false SELECT dag_id, is_stale, bundle_name FROM dag WHERE dag_id = 'bundle_bug_test'; -- bundle_bug_test | false | ex_dag_bundle ``` So in my environment, the bundle itself is correctly marked as inactive, but the DAG belonging to that bundle is still not marked as stale. -- 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]
