Bug 1771355 - Bare Metal Host's 'Ready' status collides with Node's 'Ready' status
Summary: Bare Metal Host's 'Ready' status collides with Node's 'Ready' status
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
high
Target Milestone: ---
: 4.3.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-12 09:02 UTC by Jiri Tomasek
Modified: 2020-01-23 11:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
UI now shows Bare Metal Host in ready state as 'Available' so the status is not confused with Node's ready state.
Clone Of:
Environment:
Last Closed: 2020-01-23 11:12:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3348 0 'None' closed Bug 1771355: Rename Ready host status to Available 2020-04-24 08:46:46 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:12:32 UTC

Description Jiri Tomasek 2019-11-12 09:02:29 UTC
Description of problem:
Bare Metal Host's 'Ready' status collides with Node's 'Ready' status since we're combining those together in some cases. Bare Metal Host's status should be called 'Available'

Related BMO issue: https://github.com/metal3-io/baremetal-operator/issues/315


Steps to Reproduce:
1. Deprovision host or register new host to get it into 'Ready' state

Actual results:
Host status is called 'Ready'


Expected results:
Host status is called 'Available'


Additional info:

Comment 4 errata-xmlrpc 2020-01-23 11:12:22 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.