-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Warnings about refusal to delete permissions on XComModelView #10331
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
i get same warning on 1.10.12 also get this: [2020-10-07 09:10:15,238] {manager.py:440} ERROR - Add View Menu Error: (MySQLdb._exceptions.IntegrityError) (1062, "Duplicate entry 'mydagname' for key 'name'") |
Hey @kaxil - are we doing anything about it in 2.0.0rc1? Or should we postpone? |
Yeah not critical --- just annoying warning. Moved to 2.1 |
i got the same warnings on
i checked the database, it's been migrated successfully |
Yeah currently we don't have migrations that remove those view permission -- but they are harmless warning that you can ignore cc @jhtimmins |
cc @jedcunningham Can you take a look at it -- the warning will show once you update from 1.10.x |
Adding 2.1 label due to report of #16155 |
For Airflow 2.1.1 similar warnings are seen in the logs: |
Same here for version 2.1.2 - just appeared on upgrade.
|
And solution? Facing similar problem in airflow 2.1.1. Unable to delete or edit list user from airflow UI (being Admin also is not allowing to edit permission of other users). |
I solved |
interesting, i tried what you said unfortunately it didn't stop the warning messages (did you have to reboot the web server?) and i can still clear on DAG Runs as an admin. what does this permission do? 😹 |
Check For example to fix this message |
@blag Can you take a look at this when you have time plz |
I think this might have been fixed in #21483. |
We can reopen if someone reports it after 2.2.5 |
Apache Airflow version:
1.10.11
Kubernetes version (if you are using kubernetes) (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-16T00:04:31Z", GoVersion:"go1.14.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-13T06:39:58Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Environment:
uname -a
): Linux airflow-web-65cb7d9cb8-qzcbv 4.15.0-1089-azure Http protocol sensor #99~16.04.1-Ubuntu SMP Fri Jun 5 15:30:32 UTC 2020 x86_64 GNU/LinuxWhat happened:
After upgrading from 1.10.10 to 1.10.11 (and also with new installs of 1.10.11) there are some permission warnings in the webserver logs:
It seems to be directly related to #9614 that @kaxil introduced for 1.10.11 which removes the
can_add
andcan_edit
permissions fromXComModelView
, but Airflow can not delete the permissions from that view because relations to those permissions still exist on the "Admin" and "Op" roles.In more technical terms, the two permissions can't be deleted from
ab_permission_view
table because each have relations to both the Admin's and Op's role_ids in theab_permission_view_role
table.What you expected to happen:
No warnings with Airflow 1.10.11
How to reproduce it:
airflow list_users
and view the outputted log messagesAnything else we need to know:
If those 4 role permissions are removed from the
ab_permission_view_role
table the warnings should stop. I think a migration needs to be added, or some logic that cleans up these role permissions is failing to do its job.The text was updated successfully, but these errors were encountered: