You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Loveleen Kaur (JIRA)" <ji...@apache.org> on 2018/08/22 07:07:00 UTC
[jira] [Commented] (AIRFLOW-43) Tasks never run in externally
triggered DAGRun
[ https://issues.apache.org/jira/browse/AIRFLOW-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588459#comment-16588459 ]
Loveleen Kaur commented on AIRFLOW-43:
--------------------------------------
Hi,
I am trying to implement example_trigger_controller_dag.py and example_trigger_target_dag.py (according to my requirements) but the execution time of target dag is approximately 7 hours more than the triggered time i.e Triggered time is in PDT but the execution time of dag is showing in UTC.
!image-2018-08-22-12-35-45-885.png!
Airflow dags run in PDT timezone , so to convert that into UTC, i updated cfg file with default_timezone = utc and restarted airflow but still getting same issue.
Please help.
> Tasks never run in externally triggered DAGRun
> ----------------------------------------------
>
> Key: AIRFLOW-43
> URL: https://issues.apache.org/jira/browse/AIRFLOW-43
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: Airflow 1.7.0
> Environment: OSX, Python 2.7.5
> Reporter: Chris Johnson
> Assignee: Siddharth Anand
> Priority: Critical
>
> I have a DAG which should only be run as needed (no schedule interval):
> dag = DAG(
> dag_id='major_integ_cycle',
> default_args=args,
> schedule_interval=None,
> )
> I attempted to start this using `airflow trigger_dag NAME` but the tasks never run. The scheduler has noted the fact that itthe DAG was triggered: INFO - Created <DagRun major_integ_cycle @ 2016-05-03 08:36:16.032474: manual__2016-05-03T08:36:16.032474, externally triggered: True>
> The tasks are currently very vanilla test cases, all look like this:
> task_mdc = op.BashOperator(
> task_id='master_data_cycle',
> bash_command='sleep 1',
> dag=dag,
> )
> Have I misunderstood? Or is not running a bug in this case?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)