Bug 1931349 - Only one rolebinding subject is shown in the console
Summary: Only one rolebinding subject is shown in the console
Status: CLOSED DUPLICATE of bug 1924437
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: cvogt
QA Contact: Gajanan More
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-22 09:24 UTC by oarribas
Modified: 2021-02-22 16:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-22 16:13:41 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description oarribas 2021-02-22 09:24:22 UTC
Description of problem:

If a rolebinding with more than one subject is created, the console only shows one of them.

Version-Release number of selected component (if applicable):

OpenShift 4.6 (probably all versions)

How reproducible:

Creating a rolebinding with several subjects and check in the console. Only one  user is shown.

Steps to Reproduce:
1. Create a rolebinding with several subjects:
$ cat proj_admin.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
  name: proj_admin
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: admin
- apiGroup: rbac.authorization.k8s.io
  kind: User
  name: test01
- apiGroup: rbac.authorization.k8s.io
  kind: User
  name: test02
- apiGroup: rbac.authorization.k8s.io
  kind: User
  name: test03

2. Apply the rolebinding:
$ oc apply -f proj_admin.yaml

3. Check in the console > project > Project Access tab, only one user is shown.

Actual results:

Only one user is shown in the console.

Expected results:

All the users in the rolebinding should be shown.

Additional info:

Comment 3 Jakub Hadvig 2021-02-22 12:45:30 UTC
Looks like a 4.6 issue in the DevConsole. Re-assigning to them.

Comment 4 Andrew Ballantyne 2021-02-22 16:13:41 UTC
This is already planned for a 4.6.z stream. See BZ#1924437

*** This bug has been marked as a duplicate of bug 1924437 ***

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