Bug 1855811 - EventListener page whitescreens if Route isn't fully created
Summary: EventListener page whitescreens if Route isn't fully created
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: Andrew Ballantyne
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1855812
TreeView+ depends on / blocked
 
Reported: 2020-07-10 14:57 UTC by Andrew Ballantyne
Modified: 2020-10-27 16:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1855812 (view as bug list)
Environment:
Last Closed: 2020-10-27 16:13:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:14:21 UTC

Description Andrew Ballantyne 2020-07-10 14:57:22 UTC 
Description of problem:

EventListener page whitescreens when it loads while the Route is still waiting back for a status.


Steps to Reproduce
1. Create EventListener
2. Go to the details page of the particular EventListener 
3. Notice the page doesn't load

Actual results:
The page doesn't load

Expected results:
The page should load without any errors

Reproducibility (Always/Intermittent/Only Once):  Always
Build Details: 4.6.0-0.nightly-2020-06-18-182334
Comment 3 Abhishek K N 2020-07-10 16:33:09 UTC 
Able to create EventListener & view details in Details page on following build

OpenShift Version: 4.6.0-0.nightly-2020-07-07-233934

Kubernetes Version: v1.18.3
Comment 6 errata-xmlrpc 2020-10-27 16:13:54 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
Note You need to log in before you can comment on or make changes to this bug.