Bug 1737415

Summary:	Utilization card is stuck in loading state when no IP is reported in machine object
Product:	OpenShift Container Platform	Reporter:	Rastislav Wagner <rawagner>
Component:	Console Metal3 Plugin	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED ERRATA	QA Contact:	Danylo Kholodov <dkholodo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, jtomasek, ncredi
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:34:43 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 Rastislav Wagner 2019-08-05 10:35:25 UTC

Comment 1 Rastislav Wagner 2019-08-05 11:24:43 UTC

Utilization card in Baremetal dashboard may get stuck in loading state if error occurred during fetching machine object or fetched machine object does not have IP reported in status field.

Comment 3 Udi Kalifon 2019-09-13 08:49:30 UTC

Hi Rastislav. How can we test this bug? I tried to edit the machine object and delete the IP but I guess the operator immediately restores the field. How can we simulate a machine with a missing IP, or is it enough that the machine has an IP now and the dashboard works?

Comment 4 Udi Kalifon 2019-09-16 14:21:22 UTC

Moving to the negative paths team. See also comment #3.

Comment 5 Danylo Kholodov 2019-09-17 07:19:07 UTC

Hi Rastislav,

Could you please provide more details as Udi mentioned at comment #3?

Comment 6 Rastislav Wagner 2019-09-17 07:31:38 UTC

To test this, you will need to somehow disable the operator either by

 - scaling the operator to 0 - see https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusterversion.md#disabling-the-cluster-version-operator which describes how to do this for CVO, you need to apply it to baremetal-operator

 - or by setting baremetal object as unmanaged - again CVO way is described here https://github.com/openshift/cluster-version-operator/blob/master/docs/dev/clusterversion.md#setting-objects-unmanaged but im not sure if it is supported by baremetal-operator. 

First option should work

Comment 7 Danylo Kholodov 2019-10-10 12:18:55 UTC

Verified, Utilization card in Baremetal Dashboard doesn't stuck anymore.

Comment 8 errata-xmlrpc 2019-10-16 06:34:43 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