Unable to use WWN to add Bare Metal Host to Red Hat OpenShift Container Platform cluster
Issue
-
Using WWN in the
rootDeviceHints
field enters theBareMetalHost
todeprovisioning
state, instead ofAvailable
$ oc -n openshift-machine-api get baremetalhost node-1 NAME STATUS STATE CONSUMER BMC HARDWARE_PROFILE ONLINE ERROR AGE node-1 OK deprovisioning ocpexample-xxxx-mahineset1-1234 virtualmedia://192.168.0.10/redfish/v1/Systems/System.Embedded.1 unknown true 1d
-
Viewing
node-1
BareMetalHost
manifest.$ oc -n openshift-machine-api get BareMetalHost node-1 -o yaml apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: node-1 spec: online: true bootMACAddress: 00:11:22:33:44:55 bmc: address: idrac-virtualmedia://10.10.10.10/redfish/v1/Systems/System.Embedded.1 disableCertificateVerification: true credentialsName: node-1-secret rootDeviceHints: wwn: "4x64cd94f0c5fd0642" # <---- wwn used in rootDeviceHints
Environment
- Red Hat OpenShift Container Platform 4.10 (RHOCP 4.10)
- Red Hat OpenShift Container Platform 4.11 (RHOCP 4.11)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.