Bug 1771355

Summary:	Bare Metal Host's 'Ready' status collides with Node's 'Ready' status
Product:	OpenShift Container Platform	Reporter:	Jiri Tomasek <jtomasek>
Component:	Console Metal3 Plugin	Assignee:	Jiri Tomasek <jtomasek>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, cvultur
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-23 11:12:22 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-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