Bug 1751767

Summary: Starting the node maintenance produces an error in browser console
Product: OpenShift Container Platform Reporter: Jiri Tomasek <jtomasek>
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: ahrechan, aos-bugs
Target Milestone: ---   
Target Release: 4.2.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: 2019-10-16 06:41:11 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 Jiri Tomasek 2019-09-12 14:37:49 UTC
Description of problem:

Starting the node maintenance produces an error in browser console:

backend.js:1 Warning: React does not recognize the `isExpanded` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `isexpanded` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
    in div (created by Expandable)
    in Expandable (created by StartingMaintenancePopoverContent)
    in StartingMaintenancePopoverContent (created by MaintenancePopover)

Apparently the @patternfly/react-core version used in console does not us isExpanded prop for controlling the state of the Expandable component.

Comment 1 Jiri Tomasek 2019-09-12 14:59:23 UTC
Update: Checking the Expandable component source at [1] shows, that isExpanded prop is incorrectly passed to the div element with remaining props
[1] https://github.com/patternfly/patternfly-react/blob/master/packages/patternfly-4/react-core/src/components/Expandable/Expandable.tsx

Comment 3 Artem Hrechanychenko 2019-09-16 10:12:12 UTC
VERIFIED

OpenShift version
    4.2.0-0.nightly-2019-09-13-040309

Comment 4 errata-xmlrpc 2019-10-16 06:41:11 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/RHBA-2019:2922