-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
airflow db clean - Dag cleanup won't run if dag is tagged #23414
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Related: #23206 |
I am seeing the same issue in 2.3.0 |
It's fixed in 2.3.2 |
I see the same issue when i run start task in one of my dags. I am using airflow 2.4.3 version. sqlalchemy.exc.IntegrityError: (psycopg2.errors.ForeignKeyViolation) update or delete on table "dag_run" violates foreign key constraint "task_instance_dag_run_fkey" on table "task_instance" |
same, I still see this error |
Any suggestions would be appreciated. |
If you are still seeing this issue, please create a new issue and describe your setup and how to reproduce it. Thanks |
Apache Airflow version
2.3.0 (latest released)
What happened
When running
airflow db clean
, if a to-be-cleaned dag is also tagged, a foreign key constraint in dag_tag is violated. Full error:What you think should happen instead
No response
How to reproduce
No response
Operating System
Debian GNU/Linux 11 (bullseye)
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==3.3.0
apache-airflow-providers-cncf-kubernetes==4.0.1
apache-airflow-providers-ftp==2.1.2
apache-airflow-providers-http==2.1.2
apache-airflow-providers-imap==2.2.3
apache-airflow-providers-microsoft-mssql==2.1.3
apache-airflow-providers-oracle==2.2.3
apache-airflow-providers-postgres==4.1.0
apache-airflow-providers-samba==3.0.4
apache-airflow-providers-slack==4.2.3
apache-airflow-providers-sqlite==2.1.3
apache-airflow-providers-ssh==2.4.3
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: