[
https://issues.apache.org/jira/browse/AIRFLOW-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004741#comment-17004741
]
ASF GitHub Bot commented on AIRFLOW-4428:
-----------------------------------------
tooptoop4 commented on pull request #6948: [AIRFLOW-4428] error if exec_date
before default_args.start_date in t…
URL: https://github.com/apache/airflow/pull/6948
…rigger_dag
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> Externally triggered DagRun marked as 'success' state but all tasks for it
> are 'None' state
> -------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-4428
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4428
> Project: Apache Airflow
> Issue Type: Improvement
> Components: DAG, DagRun, scheduler
> Affects Versions: 1.10.3
> Environment: LocalExecutor, 16cpu amazon linux, airflow 1.10.3, mysql
> RDS meta
> Reporter: t oo
> Priority: Critical
> Attachments: Screenshot from 2019-05-10 10-42-53.png, graph.png
>
>
> Dagrun status showing success for a given execdate but:
> * all tasks are white in graph/tree view
> * on cli running airflow task_state for any of the tasks showing in the
> graph/tree view returns None
> * taskinstance view shows no tasks for the given dagid
> This dag has 800 tasks, non_pooled_task_slot_count is 2000, max_tis_per_query
> is 2000, no pools created/assigned to the dag
> This is an externally triggered dag, all my dags are purely externally
> triggered.
> For execdates 20150101, 20160101, 20170101 getting this issue but 20180101
> works. Maybe it has something to do with this line in my dag mentioning 2017
> ---> default_args = {'owner': 'airflow','start_date': dt.datetime(2017, 6,
> 1),'retries': 0,'retry_delay': dt.timedelta(minutes=5),}
> As per comments below this issue was introduced in 1.10.3. release, i suspect
> the below jira caused it:
> * https://github.com/apache/airflow/pull/4808/files
> (https://issues.apache.org/jira/browse/AIRFLOW-3982)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
