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

Bug 1757319

Summary:	When registering nodes from the GUI, they are stuck in "powering on" state
Product:	OpenShift Container Platform	Reporter:	Udi Kalifon <ukalifon>
Component:	Console Metal3 Plugin	Assignee:	Jiri Tomasek <jtomasek>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, cvultur, jrist
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 21:26:11 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 Udi Kalifon 2019-10-01 08:34:17 UTC

Description of problem:
When registering a baremetal host from the GUI, it hangs right at the beginning in the "powering on" stage


How reproducible:
100%


Steps to Reproduce:
1. From the baremetal hosts page, register the worker node which was used as the provisioner


Actual results:
The new host never gets past the "powering on" stage


Additional info:
May be related to https://bugzilla.redhat.com/show_bug.cgi?id=1757316 [Registered baremetal hosts are registered in the "default" namespace instead of openshift-machine-api]

Comment 2 Constantin Vultur 2019-11-08 14:42:14 UTC

This is fixed

Added a new BMH , with fake IPMI. 
In about 8 minutes the Status moved to "Registration Error" and with the details:
"Failed to get power state for node 6e486cbd-4042-4d93-8f23-3c1b28d455fa. Error: IPMI call failed: power status."

Given that there was not possibility to have and end-to-end system installed,
I tested this locally in a combination of 'yarn dev' and ./bin/bridge
The local yarn was poining to a system running     4.3.0-0.ci-2019-10-30-082153

The git console log:
commit 6d8ab1f335135d959b8943b09fb172185d785fe4 (HEAD -> master, origin/release-4.4, origin/release-4.3, origin/master, origin/HEAD)
Merge: e38f53c73 8450c4d9b
Author: OpenShift Merge Robot <openshift-merge-robot.github.com>
Date:   Fri Nov 8 13:28:09 2019 +0100

Comment 3 Constantin Vultur 2019-11-08 14:46:41 UTC

Noting that, the system had CNV installed by hand , from https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/master/deploy/deploy.sh

Comment 5 errata-xmlrpc 2020-05-13 21:26:11 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