[
https://issues.apache.org/jira/browse/AIRFLOW-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561356#comment-16561356
]
Brian Kleszyk commented on AIRFLOW-695:
---------------------------------------
Also appear still have this issue in 1.8.1. This was supposedly fixed by 1.8.1.
> Retries do not execute because dagrun is in FAILED state
> --------------------------------------------------------
>
> Key: AIRFLOW-695
> URL: https://issues.apache.org/jira/browse/AIRFLOW-695
> Project: Apache Airflow
> Issue Type: Bug
> Components: DagRun
> Reporter: Harvey Xia
> Priority: Blocker
> Labels: executor, scheduler
>
> Currently on the latest master commit
> (15ff540ecd5e60e7ce080177ea3ea227582a4672), running on the LocalExecutor,
> retries on tasks do not execute because the state of the corresponding dagrun
> changes to FAILED. The task instance then gets blocked because "Task
> instance's dagrun was not in the 'running' state but in the state 'failed',"
> the error message produced by the following lines:
> https://github.com/apache/incubator-airflow/blob/master/airflow/ti_deps/deps/dagrun_exists_dep.py#L48-L50
> This error can be reproduced with the following simple DAG:
> {code:title=DAG.py|borderStyle=solid}
> dag = models.DAG(dag_id='test_retry_handling')
> task = BashOperator(
> task_id='test_retry_handling_op',
> bash_command='exit 1',
> retries=1,
> retry_delay=datetime.timedelta(minutes=1),
> dag=dag,
> owner='airflow',
> start_date=datetime.datetime(2016, 2, 1, 0, 0, 0))
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
