Uploaded image for project: 'Apache Airflow'
  1. Apache Airflow
  2. AIRFLOW-6742

Task instance state set to failed even though the Pod succeeded when using KubernetesExecutor

    XMLWordPrintableJSON

    Details

      Description

      When running a KubernetesPodOperator task with the KubernetesExecutor, the Pod succeeds but Airflow sets the task instance state to Failed.

      Attached files:

      • k8s_pods.png - KubernetesExecutor pod and KubernetesPodOperator pod both succeeded
      • kubernetes_executor_logs - Launched the KubernetesPodOperator successfully
      • airflow_scheduler_logs - "Found matching task with current state failed"
      • failed_task_instance - The failed task instance in the airflow UI
      • failed_dag_run - The failed dag run in the airflow UI

      It seems that the database is being updated with task state of failed, but I'm not sure whereabouts this state is being changed. Here is the line where the KubernetesExecutor queries the database and finds a failed task.

       

        Attachments

        1. airflow_scheduler_logs.txt
          2 kB
          Andrew Cleland
        2. failed_dag_run.png
          8 kB
          Andrew Cleland
        3. failed_task_instance.png
          18 kB
          Andrew Cleland
        4. kubernetes_executor_logs.txt
          3 kB
          Andrew Cleland
        5. k8s_pods.png
          48 kB
          Andrew Cleland
        6. airflow_scheduler_logs_full.txt
          4.69 MB
          Andrew Cleland

          Activity

            People

            • Assignee:
              dimberman Daniel Imberman
              Reporter:
              uqaclela Andrew Cleland
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: