brki opened a new issue, #60868: URL: https://github.com/apache/airflow/issues/60868
### Apache Airflow version 3.1.6 ### If "Other Airflow 3 version" selected, which one? _No response_ ### What happened? After calling `airflow dags reserialize`, without any change to the file(s) where the DAG is defined, multiple entries per DAG are created in `serialized_dag` / `dag_code` / `dag_version` tables, but **only for DAGs which have a task with a `task_id` that starts with one of the letters a-o.** ### What you think should happen instead? New entries should only be created in serialized_dag / dag_code / dag_version tables when the DAG changes. Irrespective of what the `task_id` is. ### How to reproduce ... will complete ... ### Operating System Debian GNU/Linux 12 (bookworm) ### Versions of Apache Airflow Providers ``` apache-airflow-providers-amazon==9.19.0 apache-airflow-providers-celery==3.15.0 apache-airflow-providers-cncf-kubernetes==10.12.0 apache-airflow-providers-common-compat==1.11.0 apache-airflow-providers-common-io==1.7.0 apache-airflow-providers-common-sql==1.30.2 apache-airflow-providers-fab==3.0.2 apache-airflow-providers-http==5.6.2 apache-airflow-providers-imap==3.10.2 apache-airflow-providers-microsoft-mssql==4.4.0 apache-airflow-providers-mysql==6.4.0 apache-airflow-providers-postgres==6.5.1 apache-airflow-providers-redis==4.4.1 apache-airflow-providers-samba==4.12.1 apache-airflow-providers-smtp==2.4.1 apache-airflow-providers-sqlite==4.2.0 apache-airflow-providers-standard==1.10.2 ``` ### Deployment Docker-Compose ### Deployment details The behaviour was reproduced locally using a vanilla docker compose installation. Image used: `apache/airflow:3.1.6` ### Anything else? It is consistently reproducible with the provided script. However, this seems to be a symptom of a larger problem with the reserialization logic. What motivated this report: on a production kubernetes cluster, we have a DAG that is creating new serialized_dag entries every time the dag-processor parses the DAG (no explicit `airflow dag reserialize`), while the task is running. That DAG uses a static start datetime, so I don't know what exactly is triggering that behaviour. ### 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]
