-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task instance details page blows up when no dagrun #8388
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Hello, I just installed Airflow for the first time, following the Quick Start guide. I ran the bash example operator (still following the guide):
And then, when I went to see how the run went, I got the error page with the mushroom cloud and the error. Now, this is on Apache Airflow v1.10.11 (latest stable), which I see was released on July 10, 2020. And this pull request was merged on April 15th. And this issue is closed. But I'm running into the same broken behavior. Here is my error page:
|
I don't have the rights to re-open this issue. Is it enough for me to comment on it here? |
I ran into this in AWS, running Amazon Linux 2.
Linux ip-172-20-2-227.us-west-2.compute.internal 4.14.165-131.185.amzn2.x86_64 #1 SMP Wed Jan 15 14:19:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux |
This fix may not have been officially released. Can you check to see if the problem is in the master version? |
Thank you for re-opening this issue. I've installed the master version:
I can't login through the Web UI, though. It's asking me for username and password. When I started the webserver, it said: [2020-08-11 18:25:27,417] {manager.py:719} WARNING - No user yet created, use flask fab command to do it. I tried, but it didn't work. Help?
|
Here is docs about your problem: https://github.com/apache/airflow/blob/master/UPDATING.md#drop-legacy-ui-in-favor-of-fab-rbac-ui |
Thank you! I figured it out, actually.
(I did read the documentation section you linked to, thank you; just after I already created an Don't laugh, but I can't figure out how to unpause the bash example operator. Instead of a sliding toggle switch, there is a checkbox. I installed airflow by running "pip3 install --user ." in the top directory of the top of master. |
I see this on my console:
|
You should compile JS files now, but this is a problematic process. Another solution: can you try to unpause the DAG with CLI and then go directly to the URL? |
Okay. I used Now the UI is showing all 22 DAGs are unpaused. update dag
set is_paused = '0'; |
I've installed JS using yarn as per the linked instructions. Now Airflow is showing 18 DAGs (before it was 22). The bash example operator DAG is gone. |
Is the issue discussed in this ticket still present in this version? |
I'm sorry, I can't tell. I don't seem to have a fully functional Airflow installation. The console (CLI) keeps telling me:
but I don't know how to do that. And the example bash operator disappeared from the UI after I did the "yarn prod run". |
I triggered the "tutorial" DAG instead (from the UI), and it looks like it ran. I can look at the task details. No mushroom cloud. So I would say this issue is fixed in master. |
I'm using 1.10.9 and seeing the same error for task details on SLA misses. Can someone comment if this has been fixed or not |
This should be fixed in the next release. See: #11328 |
Closed by #11343 This will be released in 1.10.13 |
Apache Airflow version:
1.10.9 although I think it would apply to 1.10.10, 1.10.8, 1.10.7, and 1.10.6
Kubernetes version (if you are using kubernetes) (use
kubectl version
):Environment:
uname -a
):Linux 567ff872fc2d 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
What happened:
If you have a DAG that has not been turned on before and you click on that DAG in the admin page and then in the DAG graph click on one of the tasks and then click on
Task Instance Details
you get the "Ooops" explosion error page. The error is:What you expected to happen:
No error page. It should have loaded the standard task instance details page.
I believe the reason that this is happening is because there is no check to see if a dagrun exists in
DagrunIdDep
:https://github.com/apache/airflow/blob/master/airflow/ti_deps/deps/dagrun_id_dep.py#L50
This is a bit of an edge case because there isn't really any reason someone should be checking out task instance details for a DAG that has never been run. That said we should probably avoid the error page.
How to reproduce it:
If you have a DAG that has not been turned on before and you click on that DAG in the admin page and then in the DAG graph click on one of the tasks and then click on
Task Instance Details
you get the "Ooops" explosion error page.Anything else we need to know:
The text was updated successfully, but these errors were encountered: