You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/06/22 22:40:42 UTC

[GitHub] [airflow] whitleykeith commented on issue #24015: KubernetesPodOperator/KubernetesExecutor: Failed to adopt pod 422

whitleykeith commented on issue #24015:
URL: https://github.com/apache/airflow/issues/24015#issuecomment-1163719748

   @BillSullivan2020 @dstandish 
   
   We were facing this after (finally) upgrading from 1.10.15 to 2.0.2. We ended up finding out that the root cause was duplicate environment variables in the worker pod definition. We checked the K8s API Server Logs and that was one of the messages around the 422 error. After tidying up our config values pods could get adopted properly. 
   
   We do get some transient errors where some pods don't get adopted with this error code: 
   
   `ERROR - attempting to adopt task <TASK_ID> in dag <DAG_ID> which was not specified by database`


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org