You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/09/03 19:41:28 UTC

[GitHub] [airflow] jmorgannht opened a new issue #18024: Dag start date is cleared when an automatic task retry is triggered

jmorgannht opened a new issue #18024:
URL: https://github.com/apache/airflow/issues/18024


   ### Apache Airflow version
   
   2.1.3 (latest released)
   
   ### Operating System
   
   Ubuntu 18.04.5 LTS
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-celery==1!1.0.1
   apache-airflow-providers-databricks==1!1.0.1
   apache-airflow-providers-ftp==1!1.1.0
   apache-airflow-providers-http==1!1.1.1
   apache-airflow-providers-imap==1!1.0.1
   apache-airflow-providers-microsoft-azure==1!2.0.0
   apache-airflow-providers-postgres==1!1.0.2
   apache-airflow-providers-sqlite==1!1.0.2
   
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   When a DAG is configured for task retries, the the dag run start date is correctly set if there are no task failures/retries.  When a retry occurs the dag run start date is blank in the UI and null in the API dagRuns response.  Doesn't matter if the retry is successful or not, the start date is wiped every time.  
   
   {
       "dag_runs": [
           {
               "conf": {},
               "dag_id": "XXXX__RPAPRNCORP_AGXEU_MO_138058",
               "dag_run_id": "scheduled__2021-08-30T16:05:51+00:00",
               "end_date": "2021-09-01T21:42:07.681597+00:00",
               "execution_date": "2021-08-30T16:05:51+00:00",
               "external_trigger": false,
               **"start_date": null,**
               "state": "failed"
           }
       ],
       "total_entries": 1
   }
   
   ### What you expected to happen
   
   A task retry should have no impact on the overall dag run start date.  
   
   ### How to reproduce
   
   Trigger a dag where at least one task has retries configured and the retry is exercised due to task failure.  
   
   ### Anything else
   
   Happens every time.  
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] potiuk closed issue #18024: Dag start date is cleared when an automatic task retry is triggered

Posted by GitBox <gi...@apache.org>.
potiuk closed issue #18024:
URL: https://github.com/apache/airflow/issues/18024


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airflow] ephraimbuddy commented on issue #18024: Dag start date is cleared when an automatic task retry is triggered

Posted by GitBox <gi...@apache.org>.
ephraimbuddy commented on issue #18024:
URL: https://github.com/apache/airflow/issues/18024#issuecomment-912819359


   I was not able to reproduce this in 2.1.3(using Sequential Executor) 
   Also tested in main using LocalExecutor. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org