Take below snipped (from an install-config.yaml) as an example. ``` hosts: - name: jetlag-bm1 role: master bmc: address: ipmi://<BMC_IP_HERE> username: <BMC_USER_HERE> password: <BMC_PASSWORD_HERE> disableCertificateVerification: true bootMACAddress: 0c:c4:7a:d3:1a --> the correct MAC is 0c:c4:7a:d3:1a:28 hardwareProfile: default rootDeviceHints: deviceName: /dev/sda ``` As you can see the MAC address misses the last two hexadecimal digits, however, the ./openshift-baremetal-install tool tries an installation that is going to fail on Ironic checks with something similar to below. ``` Jan 31 08:56:19 localhost bootkube.sh[5810]: "99_openshift-cluster-api_hosts-1.yaml": failed to create baremetalhosts.v1alpha1.metal3.io/jetlag-bm2 -n openshift-machine-api: BareMetalHost.metal3.io "jetlag-bm2" is invalid: spec.bootMACAddress: Invalid value: "0c:c4:7a:a4:eb": spec.bootMACAddress in body should match '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}' ``` Maybe we could detect this typo from the beginning similar to the validations that are done for apiVIP, and ingressVIP.
https://github.com/metal3-io/baremetal-operator/pull/1087 is for update cases.
https://github.com/openshift/installer/pull/5652 is for the install-config
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069