Bug 1840105 - Bare metal host status is Unknown / Powering on
Summary: Bare metal host status is Unknown / Powering on
Keywords:
Status: CLOSED DUPLICATE of bug 1840090
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Steven Hardy
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 11:29 UTC by Constantin Vultur
Modified: 2020-05-26 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 16:34:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
BMH status unknown powering on (167.42 KB, image/png)
2020-05-26 11:29 UTC, Constantin Vultur
no flags Details

Description Constantin Vultur 2020-05-26 11:29:10 UTC
Created attachment 1692238 [details]
BMH status unknown powering on

Description of problem:


Version-Release number of selected component (if applicable):
OCP 4.5.0-0.nightly-2020-05-26-063751

How reproducible:


Steps to Reproduce:
1. Install OCP 4.5
2. Under Compute select Bare Metal Hosts
3.

Actual results:
The master nodes appear with status Unknown / Powering On while the cluster is functional.
This might be an side effect of https://bugzilla.redhat.com/show_bug.cgi?id=1801238 where the link between the master nodes and bmh is added via the installer. 

Expected results:
Status to be as powered on, given that bmh is working ok

Additional info:
$ oc get nodes
NAME         STATUS   ROLES    AGE    VERSION
master-0-0   Ready    master   100m   v1.18.2
master-0-1   Ready    master   100m   v1.18.2
master-0-2   Ready    master   100m   v1.18.2
worker-0-0   Ready    worker   64m    v1.18.2
worker-0-1   Ready    worker   72m    v1.18.2


$ oc get bmh -A
NAMESPACE               NAME                   STATUS   PROVISIONING STATUS   CONSUMER                                 BMC                                                                                    HARDWARE PROFILE   ONLINE   ERROR
openshift-machine-api   openshift-master-0-0                                  ocp-edge-cluster-cdv2-0-master-0         redfish://192.168.123.1:8000/redfish/v1/Systems/f83113a8-4a75-44d0-ab1a-b5095c9cdd4c                      true     
openshift-machine-api   openshift-master-0-1                                  ocp-edge-cluster-cdv2-0-master-1         redfish://192.168.123.1:8000/redfish/v1/Systems/9283fc35-2cca-4037-9c98-6e6918a2ebee                      true     
openshift-machine-api   openshift-master-0-2                                  ocp-edge-cluster-cdv2-0-master-2         redfish://192.168.123.1:8000/redfish/v1/Systems/9a818b17-4ac9-49e2-8576-c450fde602a2                      true     
openshift-machine-api   openshift-worker-0-0   OK       provisioned           ocp-edge-cluster-cdv2-0-worker-0-wp6dj   redfish://192.168.123.1:8000/redfish/v1/Systems/a3121a01-275a-47fd-833e-7f9841996888   unknown            true     
openshift-machine-api   openshift-worker-0-1   OK       provisioned           ocp-edge-cluster-cdv2-0-worker-0-jr79g   redfish://192.168.123.1:8000/redfish/v1/Systems/79f9ce2b-9bcf-4e3a-85d9-4dfb8d9d728d   unknown            true     


$ oc get machines -A
NAMESPACE               NAME                                     PHASE     TYPE   REGION   ZONE   AGE
openshift-machine-api   ocp-edge-cluster-cdv2-0-master-0         Running                          111m
openshift-machine-api   ocp-edge-cluster-cdv2-0-master-1         Running                          111m
openshift-machine-api   ocp-edge-cluster-cdv2-0-master-2         Running                          111m
openshift-machine-api   ocp-edge-cluster-cdv2-0-worker-0-jr79g   Running                          89m
openshift-machine-api   ocp-edge-cluster-cdv2-0-worker-0-wp6dj   Running                          89m


$ oc get bmh openshift-master-0-0 -n openshift-machine-api -o yaml
....
  operationalStatus: ""
  poweredOn: false
  provisioning:
    ID: ""
    image:
      checksum: ""
      url: ""
    state: ""
  triedCredentials: {}

Comment 1 Honza Pokorny 2020-05-26 16:34:37 UTC

*** This bug has been marked as a duplicate of bug 1840090 ***


Note You need to log in before you can comment on or make changes to this bug.