Bug 1830096

Summary:	Opening topology sidepanel on some of the helm charts break the UI
Product:	OpenShift Container Platform	Reporter:	Rohit Rai <rorai>
Component:	Dev Console	Assignee:	Rohit Rai <rorai>
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.5	CC:	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:34:07 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 Rohit Rai 2020-04-30 20:17:18 UTC

Description of problem: Some of the Helm Charts break the UI when side panel is opened in topology. One such example is `IBM object storage plugin` chart from our catalog. Elasticsearch also has the same problem.

Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce:
1. Go to helm catalog.
2. install `IBM Object Storage Plugin` chart.
3. Select the helm release on side panel or open resources tab on side panel for that release.

Actual results: The UI breaks with white screen.

Expected results: It should show the resources tab in side panel.

Reproducibility (Always/Intermittent/Only Once): Always.

Build Details:
Additional info:

Comment 3 Gajanan More 2020-06-10 10:56:46 UTC

As we are unable to install the 'IBM Object Storage Plugin', I installed 'Elasticsearch v7.7.1'. 
I validated the bugzilla on:
Build:4.5.0-0.nightly-2020-06-09-223121
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 4 errata-xmlrpc 2020-07-13 17:34:07 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