-
Notifications
You must be signed in to change notification settings - Fork 16.8k
start_date should not be present in links from dashboard for queued and scheduled runs #49573
Copy link
Copy link
Closed
Labels
AIP-38Modern Web ApplicationModern Web Applicationaffected_version:3.0Issues Reported for 3.0Issues Reported for 3.0affected_version:main_branchIssues Reported for main branchIssues Reported for main brancharea:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.good first issuekind:bugThis is a clearly a bugThis is a clearly a bugpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Milestone
Description
Apache Airflow version
main (development)
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Some of the states like dagrun in queued state, task instance in scheduled state will not have any start_date in the database. On trying to click on these state links from the dashboard the start_date value is added to the link to task instances/dagruns list page and it tries to filter them with start_date but since the start_date is null in db they are not filtered.
Also queued is not filled in the dashboard for dagruns since queued dagrun won't have start_date. This looks like something that needs to be fixed in the backend.
What you think should happen instead?
start_date should be removed for the links from dashboard for states that will not have start_date set.
How to reproduce
- Set the pool size to 0.
- Trigger a dagrun to have the task instance in scheduled state.
- Stop the scheduler.
- Trigger a dagrun to have the dagrun in queued state.
- Try clicking on scheduled state for task instance or queued state for dagrun in the dashboard.
- The resource will not be listed in the list page
Operating System
Ubuntu 20.04
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
AIP-38Modern Web ApplicationModern Web Applicationaffected_version:3.0Issues Reported for 3.0Issues Reported for 3.0affected_version:main_branchIssues Reported for main branchIssues Reported for main brancharea:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.good first issuekind:bugThis is a clearly a bugThis is a clearly a bugpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release