-
Notifications
You must be signed in to change notification settings - Fork 612
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
Bug 2018234: Fix that user settings ConfigMap is also created for users with restricted access #10705
Bug 2018234: Fix that user settings ConfigMap is also created for users with restricted access #10705
Conversation
@jerolimov: This pull request references Bugzilla bug 2018234, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
11b9055
to
4aaf47e
Compare
@jerolimov: This pull request references Bugzilla bug 2018234, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
@jerolimov: This pull request references Bugzilla bug 2018234, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @invincibleJai @sahil143 |
/retest |
4aaf47e
to
2f5e3d4
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
verified locally works as expected.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerolimov, sahil143 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@jerolimov: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@jerolimov: All pull requests linked via external trackers have merged: Bugzilla bug 2018234 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.9 |
@jerolimov: #10705 failed to apply on top of branch "release-4.9":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2018234
Analysis / Root cause:
In #9153 we changed the implementation to save the user settings automatically to the browser localStorage instead of ConfigMap when the watcher returns a 404 Not Found. Previously this check was done after the
createConfigMap
call and checks for 403 Forbidden and 404 Not Found.The fetch call and watcher returns only 404 Not Found for kubeadmins or other cluster users with access to the
openshift-console-user-settings
namespace. But for users with restricted access, these API calls return a 403 Forbidden instead.Previously the
createConfigMap
endpoint (POST /api/console/user-settings
) was never called:Solution Description:
We need to call
createConfigMap
also if the API returns 403 Forbidden.Open the console the first time as kubeadmin:
Open the console the first time as restricted user:
Screen shots / Gifs for design review:
No UI change
Unit test coverage report:
Added / updated some tests
Test setup:
openshift-console-user-settings
namespace.User settings should be created when opening the console the first time and updated/saved after that in the ConfigMap.
Browser conformance: