Bug 1828128

Summary: Error occurs when adding access in Project Access page
Product: OpenShift Container Platform Reporter: Debsmita Santra <dsantra>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:31:39 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:
Description Flags
Edit role can be given to user none

Description Debsmita Santra 2020-04-27 06:07:32 UTC 
Description of problem:
In the project Access page, when trying to add Access it's throwing an error saying `rolebindings.rbac.authorization.k8s.io "cluster-samples-operator-openshift-<role>" not found`.

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

How reproducible:
Always

Steps to Reproduce:
1. Go to Project in the Developer Perspective
2. Click on the `Project Access` tab
3. Click on `Add Access` & try creating a role binding by adding user name and role

Actual results:
Error occurs saying `rolebindings.rbac.authorization.k8s.io "cluster-samples-operator-openshift-<role>" not found`.

Expected results:
Access should be added successfully

Additional info:
Comment 3 Gajanan More 2020-04-28 12:15:37 UTC 
Created attachment 1682452 [details]
Edit role can be given to user
Comment 4 Gajanan More 2020-04-28 12:16:11 UTC 
I have validated the bugzilla on:
Build: 4.5.0-0.ci-2020-04-27-195432
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the shared screenshot.
Marking this bugzilla as verified.
Comment 5 errata-xmlrpc 2020-07-13 17:31:39 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-2020:2409