Bug 2036662 - In a freshly installed OSD cluster, the "Installed Operators" page doesn't work (you get a blank page)
Summary: In a freshly installed OSD cluster, the "Installed Operators" page doesn't wo...
Keywords:
Status: CLOSED DUPLICATE of bug 2028286
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-03 14:25 UTC by Udi Kalifon
Modified: 2022-01-03 18:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-03 18:23:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Udi Kalifon 2022-01-03 14:25:25 UTC
Description of problem:
After installing OSD and logging in to the new cluster, you can't check the "Installed Operators"  in the cluster because the page doesn't load at all. Even the navigation and header bars are gone - the page is just a full blank white square.

After installing an add-on or two, like the data science or GPU add-ons, the page starts to work.


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


How reproducible:
100%


Steps to Reproduce:
1. Install a new OSD cluster. I installed with 3 masters and 2 workers.
2. Add an idp to the cluster so you can log in.
3. Log in to the console.
4. Switch from developer view to administrator view
5. Navigate to Operators -> Installed Operators


Actual results:
Everything is gone from the browser page, you end up with a blank white sheet


Expected results:
The installed operators page


Additional info:
You see an undefined error in the browser console, but it doesn't help much because it is minified:
TypeError: a is undefined
    fe clusterserviceversion-chunk-e820db5d81d37facd365.min.js:1
    ea vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    zs vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    _c vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    bc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    vc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    lc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Ui vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    unstable_runWithPriority vendors~main-chunk-775bdf2446b829c23bc0.min.js:187283
    zi vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Ui vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Hi vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    oc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    enqueueSetState vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    setState vendors~main-chunk-775bdf2446b829c23bc0.min.js:186937
    loadComponent main-chunk-190a736be3d1ed39d570.min.js:1
    promise callback*loadComponent main-chunk-190a736be3d1ed39d570.min.js:1
    componentDidMount main-chunk-190a736be3d1ed39d570.min.js:1
    us vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    xc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    unstable_runWithPriority vendors~main-chunk-775bdf2446b829c23bc0.min.js:187283
    zi vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    xc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    lc vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Ui vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    unstable_runWithPriority vendors~main-chunk-775bdf2446b829c23bc0.min.js:187283
    zi vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Ui vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Hi vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Pe vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970
    Kt vendors~main-chunk-775bdf2446b829c23bc0.min.js:186970

Comment 1 Jakub Hadvig 2022-01-03 18:23:08 UTC
This issue was fixed in https://bugzilla.redhat.com/show_bug.cgi?id=2028286 and is shipped in 4.9.12 version

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


Note You need to log in before you can comment on or make changes to this bug.