Bug 1768616 - Console shows nodes that aren't bare metal nodes as "powered off"
Summary: Console shows nodes that aren't bare metal nodes as "powered off"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.3.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-04 20:07 UTC by Samuel Padgett
Modified: 2020-01-23 11:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Version: 4.3.0-0.ci-2019-11-04-125204 Cluster ID: 76dd3e00-7385-4851-8d41-7b74ed2800ab
Last Closed: 2020-01-23 11:10:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
All nodes on an AWS install say "powered off" (109.68 KB, image/png)
2019-11-04 20:07 UTC, Samuel Padgett
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3246 0 'None' 'closed' 'Bug 1768616: Allow gating RoutePage extensions by feature flags' 2019-11-25 11:07:55 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:11:05 UTC

Description Samuel Padgett 2019-11-04 20:07:49 UTC
Created attachment 1632720 [details]
All nodes on an AWS install say "powered off"

See screenshot. This is an AWS install.

Comment 1 Jiri Tomasek 2019-11-04 21:06:26 UTC
This is caused by RoutePage extensions not supporting gating by feature flags, so the routes introduced by metal3 plugin are always enabled. IIUC the gating was supposed to be introduced by https://github.com/openshift/console/pull/2269. I'll investigate the workaround.

Comment 5 Udi Kalifon 2019-11-19 11:49:18 UTC
Verified with a locally running cluster from 2019-11-19 and an AWS setup version: 4.3.0-0.ci-2019-11-17-192542

Comment 7 errata-xmlrpc 2020-01-23 11:10:52 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-2020:0062


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