-
Bug
-
Resolution: Done-Errata
-
Major
-
4.12.0
Description of problem:
BMH is showing powered off even when node is up, this is causing cu's software to behave incorrectly due to incorrect status on BMH $ oc get bmh -n openshift-machine-api control-1-ru2 -o json | jq '.status|.operationalStatus,.poweredOn,.provisioning.state' "OK" false "externally provisioned" Following error can be seen: 2023-10-10T06:05:02.554453960Z {"level":"info","ts":1696917902.5544183,"logger":"provisioner.ironic","msg":"could not update node settings in ironic, busy","host":"openshift-machine-api~control-1-ru4"}
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.Launch the cluster with OCP v4.12.32 on Lenovo servers 2. 3.
Actual results:
It is giving false report of node status
Expected results:
It should report correct status of node
Additional info:
- clones
-
OCPBUGS-21777 BMH keep showing power status as off while IMM is powered on
- Closed
- depends on
-
OCPBUGS-21777 BMH keep showing power status as off while IMM is powered on
- Closed
- is cloned by
-
OCPBUGS-30629 [4.13] BMH keep showing power status as off while IMM is powered on
- Closed
- is depended on by
-
OCPBUGS-30629 [4.13] BMH keep showing power status as off while IMM is powered on
- Closed
- links to
-
RHBA-2024:0050 OpenShift Container Platform 4.14.z bug fix update