Bug 2033328 - Missing Role Bindings into groups of users
Summary: Missing Role Bindings into groups of users
Keywords:
Status: CLOSED DUPLICATE of bug 2040616
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jon Jackson
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-16 14:25 UTC by Giuseppe
Modified: 2022-02-04 19:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-04 19:24:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Under "Developer" Group i have 3 RoleBindings associated not shown (108.41 KB, image/png)
2021-12-16 14:25 UTC, Giuseppe
no flags Details

Description Giuseppe 2021-12-16 14:25:37 UTC
Created attachment 1846594 [details]
Under "Developer" Group i have 3 RoleBindings associated not shown

Description of problem:
Hi all, after upgrading from 4.8 to 4.9 into "RoleBindings" Tab (under User Management --> Groups --> click on any group name) the all RoleBindings are now missing.

In the list of RoleBindings (under User Management --> RoleBindings) instead they are present here

Version-Release number of selected component (if applicable):
4.9.0-0.okd-2021-12-12-025847

How reproducible:
Create a new Binding into a Group

Steps to Reproduce:
1.Create a example Group under User Management > Groups
2.Into Group created click on RoleBindings tabs 
3.click on "Create binding" with any values and submit

Actual results:
empty list of RoleBindings under Group detail page

Expected results:
List of RoleBindings created

Additional info:

Comment 2 Giuseppe 2022-01-29 17:40:01 UTC
Hi all,

this problem is solved in the following version: 4.9.0-0.okd-2022-01-29-035536

Comment 3 Jon Jackson 2022-02-04 19:24:29 UTC

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


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