-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Grid page visibility in the latest 2.3.1 release #23960
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
WebServer log contains:
|
Looks similar to problem in pull 23332 I can't go deeper. This is my limit of understanding. |
@stepanof you can try to delete old dag dagruns at /dagrun/list/ |
Same problem here ! I have some DAGS that are not showing up in the grid layout. I suspect that the cause is some problems on the permission due to problem with AUTH_LDAP config that I have. |
@gbonazzoli @stepanof almost for sure the problem is Duplicate of #23908 which is already solved in (very soon) 2.3.2 release where #23947 fixes it. It woudl be great if the both of you test the 2.3.2 RC1 that should appear likely within hours. |
@potiuk I will be happy to test 2.3.2 RC1. Please let me know how I can get it. |
Yep. Once we get it out you will be able to install it via |
@potiuk what about docker image? Are you going to publish 2.3.2rc1 to docker hub? |
Just being pushed. 3.7 is out already. |
All regular images ready. Now preparing slim images. |
Great, thanks a lot! I will be back soon with feedback about Grid visibility :) |
Hi! |
Closing as this is a dup of #23908 and is fixed by #23947. Thanks for the report and testing rc1 @stepanof & @gbonazzoli. I invite you both to test 2.3.2rc2 and vote on the release: https://lists.apache.org/thread/08x514oto8r7359qk44dqh7297270dd5 Btw, if you do ever want to downgrade in the future, you have to downgrade while still on 2.3.1, as that version has the migrations between 2.3.0 and 2.3.1, while 2.3.0 does not. So remember to downgrade the db first, then roll back to the old image. |
I've just upgraded to 2.3.2rc2 and everything is ok. We were running 2.3.2rc1 on production since last monday and we had non problem at all. |
Thanks for confirmiing @gbonazzoli :). Great to get such feedback from our users when release a bug fix ! |
Apache Airflow version
2.3.1 (latest released)
What happened
Hello team!
I have faced the problem with Grid visibility in the latest 2.3.1 release.
My issue (example)
Grid:
Code in the end of dag code:
Grid after deleting (Telegram alert task disappeared):
Grid after triggering dag again:
Grid:
PS:
As I remember in 2.3.0 there wasn't such bug.
I tried to roll back airflow image (from 2.3.1 to 2.3.0) and restart containers but faced error during starting webserver:
alembic.util.exc.CommandError: Can't locate revision identified by '1de7bc13c950'
I see the same error when try to execute such command:
airflow db downgrade --to-version 2.3.0
Please help to me to roll back the airflow version or may be I can get some patch which fix this bug.
What you think should happen instead
The Grid must be visible at any time at any case
How to reproduce
Steps to reproduce:
Operating System
NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian
Versions of Apache Airflow Providers
apache-airflow-providers-amazon==3.3.0
apache-airflow-providers-celery==2.1.4
apache-airflow-providers-docker==2.6.0
apache-airflow-providers-elasticsearch==3.0.3
apache-airflow-providers-google==6.8.0
apache-airflow-providers-grpc==2.0.4
apache-airflow-providers-hashicorp==2.2.0
apache-airflow-providers-http==2.1.2
apache-airflow-providers-imap==2.2.3
apache-airflow-providers-microsoft-azure==3.8.0
apache-airflow-providers-microsoft-mssql==2.1.3
apache-airflow-providers-mysql==2.2.3
apache-airflow-providers-odbc==2.0.4
apache-airflow-providers-postgres==4.1.0
apache-airflow-providers-redis==2.0.4
apache-airflow-providers-sendgrid==2.0.4
apache-airflow-providers-sftp==2.6.0
apache-airflow-providers-sqlite==2.1.3
apache-airflow-providers-ssh==2.4.3
apache-airflow-providers-telegram==2.0.4
apache-airflow-providers-vertica==2.1.3
Deployment
Docker-Compose
Deployment details
No response
Anything else
Many dags became unvisible on the Grid page and it is critical for us
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: