Bug 1769915

Summary: Node secondary status shows "Host is powered off" when no host is attached to the node yet
Product: OpenShift Container Platform Reporter: Jiri Tomasek <jtomasek>
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, cvultur
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-01-23 11:11: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 Jiri Tomasek 2019-11-07 17:01:32 UTC
Description of problem:
During the process of node being created, host power status is shown even when there is no host assigned through machine to the node yet.

Version-Release number of selected component (if applicable):


Steps to Reproduce:
1. Deprovision worker host by scaling down the worker MachineSet
2. Start provisioning the host by scaling the MachineSet back up
3. Wait till the host is successfully provisioned
4. Go to Compute > Nodes, wait for the new Node to show up
5. While new node is being created ('Not ready' status + machine is not linked) there is "Host powered off" secondary status displayed.

Actual results:
5. While new node is being created ('Not ready' status + machine is not linked) there is "Host powered off" secondary status displayed.


Expected results:
5. Until new node has machine linked there should not be any message regarding host power status.

Comment 4 errata-xmlrpc 2020-01-23 11:11: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-2020:0062