Bug 1805118

Summary: Explore page crash and display empty page
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, jokerman, spadgett
Target Milestone: ---   
Target Release: 4.5.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-03-25 03:02:51 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 XiaochuanWang 2020-02-20 09:59:41 UTC
Description of problem:
When user click Explore under Home, page crash and display as empty page. 

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-19-173908

How reproducible:
Always

Steps to Reproduce:
1. User click Home->Explore
2.
3.

Actual results:
Page crash. There is error from browser dev debug console:
vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445 RangeError: Invalid array length
    at n (api-explorer-chunk-96f23317478f108f3050.min.js:1)
    at api-explorer-chunk-96f23317478f108f3050.min.js:1
    at zi (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)
    at Zc (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)
    at Bc (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)
    at Rc (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)
    at kc (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)
    at vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445
    at e.unstable_runWithPriority (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349739)
    at uo (vendors~main-chunk-1593bbd2862ada029f0c.min.js:349445)

Expected results:
Page should direct to correct page and display normally.

Additional info:

Comment 1 Samuel Padgett 2020-02-20 14:52:58 UTC
I can't reproduce. This might be specific to the data in your cluster (maybe a specific CRD you have). Is this a cluster I can connect to?

Comment 2 XiaochuanWang 2020-03-25 03:02:51 UTC
It happened on different 4.5 clusters, but now it does not reproduced.
Checked on nightly builds: 4.5.0-0.nightly-2020-03-24-202402, 4.5.0-0.nightly-2020-03-24-224409, 4.5.0-0.ci-2020-03-25-010519

This issue could be closed. If hit it again (which obviously easy to track), will provide more details about cluster especially keep an eye on CRD. Thanks for the hint!

Comment 3 XiaochuanWang 2020-03-25 03:32:29 UTC
4.4 also does not reproduce: checked on 4.4.0-0.nightly-2020-03-23-115620,

Comment 4 Samuel Padgett 2020-03-25 13:09:23 UTC
This is the same underlying problem as bug 1811886 and was specific to a specific build.

*** This bug has been marked as a duplicate of bug 1811886 ***