Bug 1703349 - Node detail page crashes when nodemaintenance_crd is missing
Summary: Node detail page crashes when nodemaintenance_crd is missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0
Assignee: Rastislav Wagner
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-26 07:58 UTC by Radim Hrazdil
Modified: 2019-07-24 20:16 UTC (History)
4 users (show)

Fixed In Version: v2.0.0-14.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:15:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:15:59 UTC

Description Radim Hrazdil 2019-04-26 07:58:41 UTC 
Description of problem:
Web-ui crashes when user navigates to a node detail page on when NodeMaintenance CRD is not created.

Error:
TypeError
Description: Cannot read property 'data' of undefined


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


How reproducible:
100%

Steps to Reproduce:
1. Navigate to a node detail page
2.
3.

Actual results:


Expected results:
Node detail page is displayed

Additional info:
Comment 1 Rastislav Wagner 2019-04-30 11:05:46 UTC 
https://github.com/kubevirt/web-ui/pull/347
Comment 2 Radim Hrazdil 2019-05-16 11:58:10 UTC 
Verified that when NodeMaintenance CRD doesn't exist, the 'Start Maintenance' is not provided in Node action dropdown and page doesn't crash.
Version 2.0.0-14.3
Comment 4 errata-xmlrpc 2019-07-24 20:15:51 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, 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/RHEA-2019:1850
Note You need to log in before you can comment on or make changes to this bug.