Bug 1906769

Summary:	topology fails to load with non-kubeadmin user
Product:	OpenShift Container Platform	Reporter:	Jeff Phillips <jephilli>
Component:	Dev Console	Assignee:	Jeff Phillips <jephilli>
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.7	CC:	aballant, aos-bugs, nmukherj, viraj
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:	Version: 4.7.0-0.nightly-2020-12-10-120835 Cluster ID: 98470e89-fdeb-4c37-997b-34370bc9ed24 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
Last Closed:	2021-02-24 15:42:30 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:

Description Jeff Phillips 2020-12-11 11:49:05 UTC

Description of problem:

Topology fails to load when a user attempts to view the topology of another more privileged user.

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


How reproducible:

always

Steps to Reproduce:

1. login as kubeadmin
2. create a new namespace
3. create a workload
4. login as a view / self provisioner user (used consoledeveloper / developer test account)
5. go to topology

Actual results:

topology is stuck on loading screen

Expected results:

topology should load and only display what the user has access to

Additional info:

Comment 3 Vikram Raj 2021-01-07 12:15:46 UTC

Verified it and issue has been fixed.
Cluster build - 4.7.0-0.nightly-2020-12-21-131655

Comment 5 errata-xmlrpc 2021-02-24 15:42:30 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633