-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.14
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
None
-
None
-
Metal Platform 264
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Unable to provisioning a BMH using Redfish virtual media using the following Baremetalhost CR: " apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: NAME namespace: openshift-machine-api spec: bmc: address: redfish-virtualmedia://x.y.z/redfish/v1/Systems/1 credentialsName: "worker-bmc-creds" disableCertificateVerification: True bootMACAddress: "MACADDRESS" externallyProvisioned: false customDeploy: method: install_coreos online: true userData: name: worker-user-data-managed namespace: openshift-machine-api preprovisioningNetworkDataName: NETWORKDATA rootDeviceHints: deviceName: "/dev/sda" " Getting the following error: " Normal Registered 2m52s metal3-baremetal-controller Registered new host Normal BMCAccessValidated 2m42s metal3-baremetal-controller Verified access to BMC Normal InspectionStarted 2m42s metal3-baremetal-controller Hardware inspection started Normal ProfileSet 2m42s metal3-baremetal-controller Hardware profile set: unknown Normal InspectionError 2m32s metal3-baremetal-controller Failed to inspect hardware. Reason: unable to start inspection: No suitable virtual media device found "
Version-Release number of selected component (if applicable):
OCP 4.14.41, Redfish 1.0.4
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Node provisioning fails at Inspection
Expected results:
Node provisions sucessfully
Additional info: