Bug 1881516

Summary: Topology fails to load after installing a Helm Chart
Product: OpenShift Container Platform Reporter: Debsmita Santra <dsantra>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:44:36 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
Topology does not fails to load after installing a Helm Chart none

Description Debsmita Santra 2020-09-22 14:58:24 UTC 
Description of problem:
Topology fails to load after installing a Helm Chart. Error logged in the browser's console says : `Cannot destructure property 'kind' of 'object null' as it is null.`

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


How reproducible:


Steps to Reproduce:
1. Install Helm Chart `Ibm Cpq Prod v3.1.0`

Actual results:
Topology fails to load

Expected results:
Topology should load without any errors

Additional info:
Comment 2 spathak@redhat.com 2020-09-24 19:43:28 UTC 
Created attachment 1716414 [details]
Topology does not fails to load after installing a Helm Chart
Comment 3 spathak@redhat.com 2020-09-24 19:44:11 UTC 
Verify on build version: 4.6.0-0.nightly-2020-09-24-095222
Browser version: Chrome 84
Comment 6 errata-xmlrpc 2020-10-27 16:44:36 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 (OpenShift Container Platform 4.6 GA Images), 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:4196