[
https://issues.apache.org/jira/browse/AIRFLOW-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533948#comment-17533948
]
Lewis John McGibbney commented on AIRFLOW-6500:
-----------------------------------------------
Hi [~mvshpavan] we also encountered this. I also saw the following ticket
https://github.com/apache/airflow/issues/17481
I am using v2.2.4 via Helm on K8s
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5",
GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean",
BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc",
Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+",
GitVersion:"v1.11.5-dirty",
GitCommit:"753b2dbc622f5cc417845f0ff8a77f539a4213ea", GitTreeState:"dirty",
BuildDate:"2018-12-03T17:48:52Z", GoVersion:"go1.10.3", Compiler:"gc",
Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.11) exceeds the
supported minor version skew of +/-1
> dependency 'Execution Date' FAILED: Execution date is in the future
> -------------------------------------------------------------------
>
> Key: AIRFLOW-6500
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6500
> Project: Apache Airflow
> Issue Type: Bug
> Components: DAG, scheduler
> Affects Versions: 1.10.6
> Reporter: Pavan Maguluri
> Priority: Major
>
> I have the below Dag with "schedule_interval" set to None and "start_date"
> set to airflow.utils.dates.days_ago(1).
> Task1 --> Task2 --> End
> When I triggered the Dag from the Web-UI it is failing with the below reason.
> Other Dags which has "schedule_interval" set to some value don't have this
> issue.
> *[2020-01-07 07:06:39,962] \{taskinstance.py:624} INFO - Dependencies not met
> for <TaskInstance: pipeline.Task1 2020-01-07T07:06:58.550778+00:00 [queued]>,
> dependency 'Execution Date' FAILED: Execution date
> 2020-01-07T07:06:58.550778+00:00 is in the future (the current date is
> 2020-01-07T07:06:39.962619+00:00).*
>
> Default Pipeline Arguments:
> {code:python}
> PIPELINE_DEFAULT_ARGS = {
> 'owner': 'owner',
> 'start_date': airflow.utils.dates.days_ago(1),
> 'depends_on_past': True,
> 'email_on_failure': False,
> 'email_on_retry': False,
> }{code}
> All the solutions that I have read online tags with schedule_interval set to
> some value and start_date being dynamic (like datetime.now()). I don't have
> either of those settings, but, still see the problem.
> Appreciate if you can shed some light to fix this issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
