-
Bug
-
Resolution: Done-Errata
-
Blocker
-
quay-v3.9.0
-
False
-
None
-
False
-
-
-
0
Description of problem:
Try to delete a organization which created by a normal user with super user account, the delete operation fails. The error message is "Failed to delete org user1-org1, HTTP403 - Unauthorized."
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.9.0-115 Index image v4.12: registry-proxy.engineering.redhat.com/rh-osbs/iib:514828 $ oc get $(oc get pod -l name=quay-operator-alm-owned -o name -n quay-enterprise) -o jsonpath='{.spec.containers[0].image}' -n quay-enterprise registry.redhat.io/quay/quay-operator-rhel8@sha256:87ed70306e56c29e3063b3b44b506c91f1431aaeecac9b47f5870da7512a6555 $ oc get $(oc get pod -l app=quay -o NAME -n quay-enterprise|head -n 1) -o jsonpath='{.spec.containers[0].image}' -n quay-enterprise registry.redhat.io/quay/quay-rhel8@sha256:d805cd3c17fb673ab8ba6e34a06e36a5999fcb1d0ae75d8af21d6574f904e2f4
How reproducible:
always
Steps to Reproduce:
1. create a normal user "user1"
2. login with "user1" and create a organization "user1-log1"
the console for user1
3. login with super user again and go to new UI
4. Try to delete organization "user1-log1"
Actual results:
Delete organization "user1-log1" by super user will get error message "Failed to delete org user1-org1, HTTP403 - Unauthorized."
delete by super user
Expected results:
Delete organization "user1-log1" by super user should be successful.
Additional info:
$ oc -n quay-enterprise rsh $(oc get pod -l app=quay -o NAME -n quay-enterprise|head -n 1) cat /conf/stack/config.yaml ALLOW_PULLS_WITHOUT_STRICT_LOGGING: false ........ FEATURE_SUPERUSERS_FULL_ACCESS: true FEATURE_UI_V2: true SUPER_USERS: - whuquay .......
Similar issue have been fixed in quay 3.8.0
- links to
- mentioned on
(7 mentioned on)
