Bug 1739351 - Bare Metal Hosts appear in status "other" instead of "OK"
Summary: Bare Metal Hosts appear in status "other" instead of "OK"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-09 06:53 UTC by Udi Kalifon
Modified: 2019-10-16 06:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:35:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2369 0 None closed Bug 1739351: Filter externally provisioned hosts as provisioned hosts 2020-12-28 13:53:57 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:35:45 UTC

Description Udi Kalifon 2019-08-09 06:53:39 UTC 
Description of problem:
In the dashboards screen, inventory card, the bare metal hosts don't have a green "check" icon even though they are healthy. When checking on the command line with "oc get baremetalhosts -n openshift-machine-api" they are all in OK status.


How reproducible:
100%


Steps to Reproduce:
1. Open the dashboards page


Actual results:
The bare metal hosts have a grey "?" status, like it's an unknown status.
Comment 1 Jiri Tomasek 2019-08-09 09:44:10 UTC 
Yes, Externally Provisioned should fall into the 'Provisioned' filter category.
Comment 3 Danylo Kholodov 2019-08-29 12:31:48 UTC 
Verified
Comment 4 errata-xmlrpc 2019-10-16 06:35:36 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
Note You need to log in before you can comment on or make changes to this bug.