Bug 1819941

Summary:	OperatorHub doesn't show up after created a ClusterRoleBinding to `aggregate-olm-view` for non-cluster admin users
Product:	OpenShift Container Platform	Reporter:	Samuel Padgett <spadgett>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.z	CC:	aos-bugs, jokerman, spadgett, tony.wu, xiaocwan, yapei
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1819940	Environment:
Last Closed:	2020-04-14 16:18:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1819940
Bug Blocks:

Description Samuel Padgett 2020-04-01 21:13:02 UTC

+++ This bug was initially created as a clone of Bug #1819940 +++

+++ This bug was initially created as a clone of Bug #1819938 +++

Description of problem:
OperatorHub view in console is depending on if the users have the permission to list package manifests and operator groups in all namespaces. 

However, after created a ClusterRoleBinding to `aggregate-olm-view` for non-cluster admin users, the OperatorHub still doesn't show up.

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

How reproducible:
100%

Steps to Reproduce:
1. Create ClusterRoleBinding and bind to a non cluster admin user
2. Log in with that user


Actual results:
Didn't see OperatorHub view

Expected results:
OperatorHub view shows up.

Additional info:

Comment 3 XiaochuanWang 2020-04-10 05:49:39 UTC

Verified on 4.3.12
After grant the role "aggregate-olm-view" to a normal user, this user can visit Operator Hub from menu.

Comment 5 errata-xmlrpc 2020-04-14 16:18:53 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:1393