-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Description
Apache Airflow version: 1.10.12
Kubernetes version (if you are using kubernetes) (use kubectl version): N/A
Environment:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release): MacOS & Linux
- Kernel (e.g.
uname -a): - Install tools:
- Others:
What happened:
I have set timezone=America/Phoenix in airflow.cfg.
When clicking on the DAG Run ID in the DAG list, it references the DAG run based on my timezone as opposed to the UTC one. Since all DAG Run IDs are comprised of UTC only, it ends up setting the Base Date to the wrong value and referencing the wrong DAG run.
What you expected to happen:
it should reference the correct DAG run.
What do you think went wrong?
When moving from DAG list to the individual DAG run view, it changes the UTC time to your timezone set in airflow.cfg and causes the mismatch.
How to reproduce it:
Set timezone to something other than UTC in airflow.cfg.
Create a normal DAG; schedule it to execute every 1 min.
Click on the Schedule button on the individual DAG view to get the DAG list.
Click on one of the entries to view the DAG run. You should notice it refers to the wrong one.
Screenshot Reference:

