Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1871821

Summary: [Assisted-4.5][Integration env] Cluster details page failed to load
Product: OpenShift Container Platform Reporter: Lital Alon <lalon>
Component: assisted-installerAssignee: Rastislav Wagner <rawagner>
assisted-installer sub component: assisted-ui QA Contact: Udi Kalifon <ukalifon>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: unspecified CC: aos-bugs, rawagner
Version: 4.5   
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:30:45 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
Cluster details page load failure none

Description Lital Alon 2020-08-24 11:21:11 UTC 
Created attachment 1712339 [details]
Cluster details page load failure

Created attachment 1712339 [details]
Cluster details page load failure

Created attachment 1712339 [details]
Cluster details page load failure

Created attachment 1712339 [details]
Cluster details page load failure

Created attachment 1712339 [details]
Cluster details page load failure

Description of problem:
After playing a bit with the Cluster details page (ran cluster and host validation tests), got to a stage where cluster details page cannot be loaded, and displays an error (see attached)



How reproducible:
Integration environment
Using QE user (nshidlin-aiqe1)

Steps to Reproduce:
1. boot 2 masters belong to CIDR-A and one master belong to CIDR-B. wait until they discovered
2. mark all role nodes to master
3. fill in all cluster parameters. In the Available Subnets put CIDR-B along with Ingress VIP and API VIP. Save changes.
4. Kill master node that belongs to CIDR-B
5. from console, choose to disable the node
6. from console, choose to enable the master node again

Actual results:
Page load error

Expected results:
Page should load

Additional info:
Ran Cluster and Hosts validation tests when reproduced. Mostly connected agents, and play with hosts interfaces, hostnames, subnet CIDR, enable/disable hosts and so. The only reproduce able scenario i could catch described above.
Comment 1 Lital Alon 2020-08-24 11:21:46 UTC 
UI ERROR:

Danger alert:Something went wrong
Error: Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    in le
    in ta
    in na
    in mn
    in Za
    in t
    in t
    in to
    in u
    in eo
    in Unknown
    in x
    in t
    in t
    in t
    in n
    in r
    in x
    in o1
    in withRouter(o1)
    in s1
    in d1
    in x
    in t
    in t
    in u
Comment 2 Lital Alon 2020-09-01 12:47:17 UTC 
Verified in Staging (deployed at: Sep, 1)
Comment 5 errata-xmlrpc 2020-10-27 16:30:45 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