[jira] [Resolved] (AIRFLOW-3658) dag.get_run_dates() goes into infinite loop in case of missing date, cause by DST switch

["Ash Berlin-Taylor (JIRA)" <ji...@apache.org>]

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

Ash Berlin-Taylor resolved AIRFLOW-3658.
----------------------------------------
    Resolution: Duplicate

> dag.get_run_dates() goes into infinite loop in case of missing date, cause by DST switch
> ----------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3658
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3658
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG
>    Affects Versions: 1.10.1
>         Environment: ubuntu 16.04
> python 3.6
> airflow 1.10.1
>            Reporter: Peter Erben
>            Priority: Major
>
> In airflow.cfg the default_timezone is Europe/Budapest. In this timezone the winter to summer DST switch happened on 2018-03-25 at 2am, when the hour skipped to 3am. This means that 2018-03-25T02:00:00 is not a valid datetime in that timezone.
> I created a dag with these parameters:
>  
> {code:java}
> start_date = datetime(2018,3,25,0,0) - timedelta(days=2)
> end_date = datetime(2018,3,25,0,0) + timedelta(days=2)
> schedule_interval  = '0 2 * * *'
> {code}
>  
> When I call dag.get_run_dates(), it never returns.
>  
> Does this mean, that Airflow fails to schedule any tasks if I try to set the Europe/Budapest timezone, and the daily time defined by the cronstring is non-existent on the day of the DST switch? 
>  



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