-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Important
Some nodes are unable to finish provisionning and are stuck in that state
[root@rhel92-ocp-vm ~]# oc get bmh -A
NAMESPACE NAME STATE CONSUMER ONLINE ERROR AGE
openshift-machine-api controller1 externally provisioned true 4d2h
openshift-machine-api worker1 provisioning openstack-data-plane true 28m
openshift-machine-api worker2 provisioning openstack-data-plane true 72m
Nov 15 19:16:07 cert77 ironic-agent[2471]: 2024-11-15 19:16:07.724 1 ERROR ironic_python_agent.inspector [-] inspector https://10.50.7.20:5050/v1/continue error 400: {"error":{"message":"Node XXXXXX is not active, its provision state is clean wait"}}
Nov 15 19:16:07 cert77 podman[2437]: 2024-11-15 19:16:07.724 1 ERROR ironic_python_agent.inspector [-] inspector https://10.50.7.20:5050/v1/continue error 400: {"error":{"message":"Node XXXXX is not active, its provision state is clean wait"}}
It also happens even if you disable node cleaning in bmh.yaml:
metadata:
annotations:
inspect.metal3.io: disabled
And:
spec:
automatedCleaningMode: disabled