deepak4babu opened a new issue, #60763:
URL: https://github.com/apache/airflow/issues/60763

   ### Apache Airflow version
   
   Other Airflow 3 version (please specify below)
   
   ### If "Other Airflow 3 version" selected, which one?
   
   3.0.6
   
   ### What happened?
   
   When upgrading airflow from 2.x to 3.06 and some dags are removed at the 
same time. The removed dags are not deactivated.
   
   We use the default config values.
   
   We suspect that the issue is due to null bundle_name for the removed dags as 
dags without bundle_names are not scanned for deactivation.
   
   ### What you think should happen instead?
   
   The removed dags should be deactivated and should be cleared from UI.
   
   ### How to reproduce
   
   Create a 2.x airflow enviroment with some dags. Upgrade the env to 3.0.6 and 
remove the dags at the same time. 
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-celery==3.12.2
   apache-airflow-providers-cncf-kubernetes==10.8.2
   apache-airflow-providers-common-compat==1.7.3
   apache-airflow-providers-common-io==1.6.2
   apache-airflow-providers-common-sql==1.27.5
   apache-airflow-providers-fab==2.4.1
   apache-airflow-providers-ftp==3.13.2
   apache-airflow-providers-http==5.3.3
   apache-airflow-providers-imap==3.9.2
   apache-airflow-providers-postgres==6.2.3
   apache-airflow-providers-smtp==2.2.0
   apache-airflow-providers-sqlite==4.1.2
   apache-airflow-providers-standard==1.6.0
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### 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]

Reply via email to