Bug 1603079
| Summary: | [converged] namespace-level Role page does not display any namespace-level rolebinding on "Role Bindings" tab page on Roles page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> | ||||
| Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.11.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-10-11 07:22:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
After created namespaced Role and namespaced Rolebinding to someone, step 4 is reproduced. (on Roles page, choose only Namespace Roles "example" -> click "example" -> click "Role Bindings") reproduced on v3.11.0-0.9.0 Image Id: registry.reg-aws.openshift.com:443/openshift3/ose-console v3.11 e03103f86278f 284MB Tested this on master and I am unable to reproduce. Steps taken to try and reproduce: 1. Start a fresh cluster with basic user (no admin login) 2. In the web console, select 'myproject' from the projects list page to make it the current project 3. Go to Roles list page 4. Click 'Create Role' 5. Use the example role that is provided by default 6. Back on the Roles list page, select only the 'Namespace roles' filter to display only the recently created Role. 7. Click the role name to navigate to the Role detail page 8. Click the Role Bindings tab, "No Role Bindings Found" message is displayed 9. Click "Create Binding" 10. Select "Namespace Role Binding" 11. Enter 'example' in role binding name field 12. Select 'myproject' in the 'Namespace' field 13. Select 'example' in the 'Role' field 14. Select 'User' in the subject field 15. Enter 'example' in the 'Subject Name' field 16. Click 'Create Binding' 17. Navigate back to the 'example' role details page and click the 'Role Bindings' tab 18. Role binding created in steps 9-16 is listed on this page Is it possible that this was tested against an image that did not include my fix? Verified on v3.11.0-0.10.0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652 |
Created attachment 1459889 [details] project rolebinding is created successfully Description of problem: When user has a project, create namespace-level role and namespace-level rolebinding in the project scope, "Role Bindings" tab pag on the Role page failed to display anything. It sends wrong request from the page. Version-Release number of selected component (if applicable): docker.io/openshift/origin-console latest 5188f5035cee 6 hours ago 259 MB openshift v3.10.18 How reproducible: Always Steps to Reproduce: 1. User create a project and choose the project. 2. User create a project-level role named "example". 3. User create a project-level rolebinding by choosing "Namespace Role Binding (RoleBinding)" and bind it to "example", check the Role Bindings menu page (see the screenshot) 4. Browse to Roles page, from "Namespace Roles" select "example" role, then check "Role Bindings" tab page Actual results: 4. There is no rolebinding. Only an error which said user can not list all clusterrolebindings.rbac.authorization.k8s.io in the cluster Expected results: 4. Since this is namespace-scoped role and rolebinding, it should not request to list all clusterrolebinding in the cluster level. Existed rolebinding should be listed. Additional info: