[ 
https://issues.apache.org/jira/browse/AIRFLOW-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yassine updated AIRFLOW-3098:
-----------------------------
    Description: 
The setup is a standard airflow install backed by sqlite db running a 
sequential executor. I created a simple dag with linear task layout as follows:

 
{quote}{{[ Create an EMR cluster ] >-> [ submit first EMR step ] >> [ check 
first step status ] >> [ submit second EMR step ] >-> [ check second step 
status ]}}
{quote}
All tasks finish and are green (nor error in the task logs) yet airflow marks 
the dag run as failed. I have no clue why.

  was:
The setup is a standard airflow install backed by sqlite db running a 
sequential executor. I created a simple dag with linear task layout as follows:

 
{quote}{{[ Create an EMR cluster ] -> [ submit first EMR step ] -> [ check 
first step status ] -> [ submit second EMR step ] -> [ check second step status 
]}}{quote}
All tasks finish and are green (nor error in the task logs) yet airflow marks 
the dag run as failed. I have no clue why.


> Dag run succeeds (all related tasks green) yet airflow marks as failed
> ----------------------------------------------------------------------
>
>                 Key: AIRFLOW-3098
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3098
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: aws, DagRun
>    Affects Versions: 1.10.0
>            Reporter: Yassine
>            Priority: Major
>
> The setup is a standard airflow install backed by sqlite db running a 
> sequential executor. I created a simple dag with linear task layout as 
> follows:
>  
> {quote}{{[ Create an EMR cluster ] >-> [ submit first EMR step ] >> [ check 
> first step status ] >> [ submit second EMR step ] >-> [ check second step 
> status ]}}
> {quote}
> All tasks finish and are green (nor error in the task logs) yet airflow marks 
> the dag run as failed. I have no clue why.



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

Reply via email to