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.
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?
Moving to the negative paths team. See also comment #3.
Hi Rastislav, Could you please provide more details as Udi mentioned at comment #3?
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
Verified, Utilization card in Baremetal Dashboard doesn't stuck anymore.
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