Bug 1691694 - "Status" page for "all projects" often goes blank
Summary: "Status" page for "all projects" often goes blank
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.1.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
: 1694402 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-22 09:40 UTC by Yanping Zhang
Modified: 2019-03-31 14:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 12:58:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
statuspage (1.92 MB, image/gif)
2019-03-22 09:40 UTC, Yanping Zhang
no flags Details

Description Yanping Zhang 2019-03-22 09:40:09 UTC
Created attachment 1546817 [details]
statuspage

Description of problem:
Cluster admin login console, go to "Home"->"Status" page, choose "all projects" in project dropdown list, the page always goes blank.

Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-03-22-002648
Console image:
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:9221ead0a479014e76c491f1f6851a0975f3309744036cd16bf5d21521c57e7e
io.openshift.build.commit.url=https://github.com/openshift/console/commit/f8e74b6a028719fd191f1cd6c5dcb30029ee3f89

How reproducible:
Always

Steps to Reproduce:
1.Cluster admin login console, go to "Home"->"Status" page, choose "all projects" in project dropdown list.
2.
3.

Actual results:
1. The page always goes blank.
JS error:
VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107 TypeError: Cannot read property 'toLowerCase' of undefined
    at VM335 main-chunk-b6ef2d27dff7c8957b1a.min.js:1
    at Array.find (<anonymous>)
    at F (VM335 main-chunk-b6ef2d27dff7c8957b1a.min.js:1)
    at t.render (VM335 main-chunk-b6ef2d27dff7c8957b1a.min.js:1)
    at h (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)
    at beginWork (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)
    at o (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)
    at a (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)
    at x (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)
    at _ (VM334 vendors~main-chunk-f17fe949efefcd42bcd2.min.js:107)

Expected results:
1. Should not show blank page.

Additional info:

Comment 1 Samuel Padgett 2019-03-22 14:07:41 UTC
I'm able to reproduce. Seeing errors about operator groups. I'm not sure why that would happen on this page.

TypeError: "n is undefined"
	a operator-group.tsx:51
	F operator-group.tsx:51
	render operator-group.tsx:51
h11React	value index.js:8
	_onResize index.js:8
	__resizeRAF__ index.js:8
	__resizeRAF__ index.js:8
 react-dom.production.min.js:13

Comment 2 Samuel Padgett 2019-03-22 15:49:41 UTC
OK I think operator-group in the comment #1 stack is just a problem with source maps for minified JS and probably a red herring.

Based on the original stack trace, I believe the error is here:

https://github.com/openshift/console/blob/master/frontend/public/components/events.jsx#L46

This would happen in an event didn't have a `Reason` property. This is uncommon, but it looks like it is an optional field:

https://github.com/kubernetes/api/blob/master/core/v1/types.go#L4640-L4644

Comment 3 Samuel Padgett 2019-03-22 15:53:24 UTC
https://github.com/openshift/console/pull/1322

Comment 4 Yanping Zhang 2019-03-25 03:08:43 UTC
4.0.0-0.nightly-2019-03-23-222829
console image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f306e62671038169609c11dafe854881f1982fde8e69f429462ebb414d547e6d
https://github.com/openshift/console/commit/4cb747009adf95fc9409714a4df52ff1e7522912
Checked on OCP 4.0 env with above version, now the status page for "all projects" works well, the bug has been fixed, so move it to Verified.

Comment 5 Samuel Padgett 2019-03-31 14:37:28 UTC
*** Bug 1694402 has been marked as a duplicate of this bug. ***


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