Description of problem: IPI bare metal deployment fails when using ilo5-virtualmedia with iLO5 nodes: Failed to prepare to deploy. Exception: An auth plugin is required to determine endpoint URL Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-02-131318 How reproducible: 100% Steps to Reproduce: 1. 1. Deploy bare metal IPI environment using ilo5-virtualmedia and iLO5 nodes: - name: openshift-master-0 role: master bmc: address: ilo5-virtualmedia://${IP}/redfish/v1/Systems/1 disableCertificateVerification: True username: admin password: pass Actual results: openstack baremetal node show 5835151e-3eeb-4f16-a25f-e2c9881741c4 | grep last_error | last_error | Failed to prepare to deploy. Exception: An auth plugin is required to determine endpoint URL Expected results: No failures Additional info:
Looks like we're missing 3 virtmedia related patches in the downstream ironic-image, I'm setting up an environment to test backports now and will submit the patches once I know nothing else is missing. The missing patch that caused the error in question is a patch that sets +[redfish] +use_swift = false
Correction, turns out its only 2 patches that were missing, see Pr here https://github.com/openshift/ironic-image/pull/69 These are needed to remove the use of swift and change the patch where grub looks for grub.cnf, I wasn't able to get a full deploy done but this was down to my network setup
The linked PR merged weeks ago, moving to MODIFIED.
[kni@provisionhost-0-0 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-06-26-215024 True False 15h Cluster version is 4.5.0-0.nightly-2020-06-26-215024 [kni@provisionhost-0-0 ~]$ oc -n openshift-machine-api exec -it metal3-6fd7b4ffb-pnk4r -c metal3-ironic-conductor -- grep -A1 \\[redfish\\] /etc/ironic/ironic.conf [redfish] use_swift = false
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409