You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/14 18:07:00 UTC

[jira] [Commented] (AIRFLOW-3319) Kubernetes Executor attempts to get the "try_number" from labels but fails

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

ASF subversion and git services commented on AIRFLOW-3319:
----------------------------------------------------------

Commit b8c475704a33b155ea4415c94657f62d37bc9f5e in airflow's branch refs/heads/master from Wyndham Blanton
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=b8c4757 ]

[AIRFLOW-3319] - KubernetsExecutor: Need in try_number in  labels if getting them later (#4163)

* Need in labels if getting them later

* has to be an int to match running keys

- otherwise  running list will never empty

* pr comments

* bad merge

* mend pep issue

* add try_numer to make_pod test


> Kubernetes Executor attempts to get the "try_number" from labels but fails
> --------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3319
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3319
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: executor, kubernetes
>    Affects Versions: 1.10.1
>            Reporter: Bo Blanton
>            Priority: Major
>             Fix For: 1.10.2
>
>
> The {{_labels_to_key}} function attempts to use the `try_number` from the k8 labels, however no such label is applied to the pod resulting in an exception.
> Modify pod executor to add this label to fix.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)