Bug 1603079 - [converged] namespace-level Role page does not display any namespace-level rolebinding on "Role Bindings" tab page on Roles page
Summary: [converged] namespace-level Role page does not display any namespace-level ro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: Jon Jackson
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 06:11 UTC by XiaochuanWang
Modified: 2018-10-11 07:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:22:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
project rolebinding is created successfully (56.48 KB, image/png)
2018-07-19 06:11 UTC, XiaochuanWang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:22:29 UTC

Description XiaochuanWang 2018-07-19 06:11:20 UTC
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:

Comment 1 Jon Jackson 2018-07-24 14:14:19 UTC
https://github.com/openshift/console/pull/287

Comment 2 XiaochuanWang 2018-07-27 03:23:19 UTC
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

Comment 3 Jon Jackson 2018-07-27 14:56:38 UTC
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

Comment 4 Jon Jackson 2018-07-27 14:57:06 UTC
Is it possible that this was tested against an image that did not include my fix?

Comment 5 XiaochuanWang 2018-07-30 06:15:45 UTC
Verified on v3.11.0-0.10.0

Comment 6 XiaochuanWang 2018-07-30 07:29:47 UTC
Original steps in Description and Comment 2, Comment 3 are same, verified by same steps.

Comment 8 errata-xmlrpc 2018-10-11 07:22:06 UTC
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


Note You need to log in before you can comment on or make changes to this bug.