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

Posted to commits@airflow.apache.org by "Tim Retout (Jira)" <ji...@apache.org> on 2021/06/11 20:07:00 UTC

[jira] [Commented] (AIRFLOW-7077) KubernetesPodOperator exit code isn't propagated

    [ https://issues.apache.org/jira/browse/AIRFLOW-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362006#comment-17362006 ] 

Tim Retout commented on AIRFLOW-7077:
-------------------------------------

I have heard a report at work that the same issue is affecting a project, and I'm attempting to find out more details.

However I have set up a fresh Airflow 2.1.0 running on GKE (using the Bitnami helm chart), and so far KubernetesPodOperator is correctly setting the failed status in my configuration.

> KubernetesPodOperator exit code isn't propagated
> ------------------------------------------------
>
>                 Key: AIRFLOW-7077
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-7077
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: operators
>    Affects Versions: 2.0.0, 1.10.7
>            Reporter: Yegor Andreenko
>            Priority: Major
>              Labels: kubernetes
>
> Now Kubernetes Pod Operator doesn't correctly return status on kubernetes job.
> If the job has failed(has in logs exit code != 0) it still has {{success}} status in airflow.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)