bparhy opened a new issue #20203: URL: https://github.com/apache/airflow/issues/20203
### Apache Airflow version 2.1.3 ### What happened We are using Airflow version 2.1.3 Using kubernetes executor We have other deployment in this k8s namespace which are running using airflow 1.10.10 and 1.10.12 etc. For the airflow version 2.1.3 we are seeing an error in the scheduler logs where it looks like the scheduler is trying to adopt pods which are scheduled by other airflow deployments. Below is the error. Failed to adopt pod <pod_id> Reason: (422) Reason: Unprocessable Entity HTTP response headers: This mainly happens for pods/task which are completed already. ### What you expected to happen Airflow scheduler should not attempt to adopt pods from other deployments. ### How to reproduce Create two airflow deployments one with version 1.10.10 and other with 2.1.3 Set up a dag in 1.10.10 with a frequency of 5 minutes and then check the logs for airflow version 2.1.3. You should see 2.1.3 scheduler trying to adopt pods with the below error Failed to adopt pod <pod_id> Reason: (422) Reason: Unprocessable Entity HTTP response headers: ### Operating System linux ### Versions of Apache Airflow Providers Not dependent on provider version ### Deployment Other 3rd-party Helm chart ### Deployment details We are deploying on k8s instance with 2 scheduler and 1 web server with airflow 2.1.3 We are using helm to deploy and metadata DB is postgres with AWS Aurora. ### Anything else _No response_ ### Are you willing to submit PR? - [X] 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]
