-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
After upgrade from Airflow 2.2.4, grid disappears for some DAGs #23588
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Video that shows the problem |
Getting the same thing - It appears to be an issue with the getTask API (there's several javascript errors in console). Most notably the /tasks endpoint for a given dag. Python version: 3.9.12
|
Hmm thats a new one. @norm would you mind taking a look at get tasks? |
Just wanted to update, that this appears to only be happening for DAGs that have TaskGroups. When viewing my "non-taskgroup" DAGs, the grid-view works as expected. When trying to select individual tasks on a DAG with task groups (and therefore have expand/collapsible grid), clicking on an individual task the entire grid view disappears. |
Can someone give us a DAG and re-production steps please? |
Also, what are the other js console errors aside from the get task endpoint? Even if that endpoint throws an error, the UI shouldn't crash |
I get first error message twice when then the second when the Grid view loads:
And finally, the following error twice when I click one of the tasks:
|
Great thanks -- the second error is likely a side effect of the first. What error appears in the webserver logs when you do the first action? |
The web server error is what I posted above... ends with:
I too am getting the same JS errors that @rotemseekingalpha is showing as well. My theory about taskgroups however, appears wrong because it's also happening on "non-taskgroup" DAGs. In my case they're "previously parsed" dags, and were there before the upgrade to 2.3.0 - so I assume there's something in the migration for these dags or that happened to them in the past that 2.3.0 just doesn't like. |
Do you have If someone can share with me a dag that exhibits this behaviour that would be very useful. |
@ashb we rely heavily on |
I'll say it for the third time: we need a DAG that has this behavoiur to reproduce and fix it please. |
@zachliu That grid view issue was caused by something else (removing a task from a DAG after it has run) to the 500 errors reported in this thread. |
Got it. At least one step: We need to make sure an error on |
I'm having the same issue: Thank you for your fix @bbovenzi! Looking forward to it in the next version! |
it's also happening for us when the user role is viewer (not logged in). (for admin role it works fine) |
We were able to determine that this issue was caused by a custom operator that erroneously had Before: |
@jpipas Do you know what error the API is failing with? (May be available in web server logs.) Ideally the web server should be a bit more resilient to this kind of user errors. |
I get the same error when I'm using AUTH_ROLE_PUBLIC = 'Admin' in webserver_config.py. |
I get the same error, but Grid View disappears almost immediately after entering that page, without clicking anything. Also I have small number of DAGs. |
@cloventt @rotemseekingalpha I'm using the official Airflow helm chart. Encountered the same error. In the chart, we use Have been able to fix this error by adding the following to the chart:
|
@kobethuwis thank you for this tip! Adding |
We have the same problem in some DAGs (others working as expected) after upgrade from 1.0.15 to 2.5.3). |
I believe I found the root cause of the problem. A new feature was introduced in 2.3.0 - "details drawer" in Grid View (#22123). Under the hood in calls As a result the On top of that #30373 introduced more improvements to the details drawer and now there's also a POST being sent to EDIT: It's not actually the details drawer itself that is problematic, but its "Mark task as" modals. |
cc: @bbovenzi @pierrejeambrun ^^ |
Apache Airflow version
2.3.0 (latest released)
What happened
After the upgrade from 2.2.4 to 2.3.0, some DAGs grid data seems missing and it renders the UI blank
What you think should happen instead
When I click the grid for a specific execution date, I expect to be able to click the tasks and view the log, render jinja templating, and clear status
How to reproduce
Run an upgrade from 2.2.4 to 2.3.0 with a huge database (we have ~750 DAGs with a minimum of 10 tasks each).
In addition, we heavily rely on XCom.
Operating System
Ubuntu 20.04.3 LTS
Versions of Apache Airflow Providers
apache-airflow apache_airflow-2.3.0-py3-none-any.whl
apache-airflow-providers-amazon apache_airflow_providers_amazon-3.3.0-py3-none-any.whl
apache-airflow-providers-ftp apache_airflow_providers_ftp-2.1.2-py3-none-any.whl
apache-airflow-providers-http apache_airflow_providers_http-2.1.2-py3-none-any.whl
apache-airflow-providers-imap apache_airflow_providers_imap-2.2.3-py3-none-any.whl
apache-airflow-providers-mongo apache_airflow_providers_mongo-2.3.3-py3-none-any.whl
apache-airflow-providers-mysql apache_airflow_providers_mysql-2.2.3-py3-none-any.whl
apache-airflow-providers-pagerduty apache_airflow_providers_pagerduty-2.1.3-py3-none-any.whl
apache-airflow-providers-postgres apache_airflow_providers_postgres-4.1.0-py3-none-any.whl
apache-airflow-providers-sendgrid apache_airflow_providers_sendgrid-2.0.4-py3-none-any.whl
apache-airflow-providers-slack apache_airflow_providers_slack-4.2.3-py3-none-any.whl
apache-airflow-providers-sqlite apache_airflow_providers_sqlite-2.1.3-py3-none-any.whl
apache-airflow-providers-ssh apache_airflow_providers_ssh-2.4.3-py3-none-any.whl
apache-airflow-providers-vertica apache_airflow_providers_vertica-2.1.3-py3-none-any.whl
Deployment
Virtualenv installation
Deployment details
Python 3.8.10
Anything else
For the affected DAGs, all the time
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: