Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1739407

Summary:	Host status does not reflect operational status and does not show errors
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:	high
Version:	4.2.0	CC:	aos-bugs, dkholodo
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:35:36 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-08-09 08:57:54 UTC

Description of problem:
baremetalhost provides 2 states: 'provisioning.state' and 'operationaStatus'. Currently getBaremetalHostStatus function gives preference to provisioning.state which is not correct. The getBaremetalHostStatus should compare the two and derive a proper BMH status.

e.g. operationalStatus: error + provisioning.state: Registering = 'registration error' + error message.

Comment 1 Danylo Kholodov 2019-08-30 09:25:06 UTC

Verified

Comment 2 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