Hide Forgot
This is quite an important piece to complete https://issues.redhat.com/browse/MPINSTALL-6. So, thanks for taking a look @zaneb.
We don't actually need to block 4.9 GA for this. We'll pudh to get the fix into a z-stream release as soon as possible.
Verified on [kni@provisionhost-0-0 ~]$ oc get clusterversion ... Cluster version is 4.9.0-0.nightly-2021-10-26-021742 Steps to reproduce: 1. Build the cluster with the Disabled provisioning and Redfish-VirtualMedia management type 2. Go through the masters and catch the boot mac addresses for available interfaces ( "enp0s3" in my case) ssh core@master-0-0 & ip a 3. Edit the provisioning CR: [kni@provisionhost-0-0 ~]$ oc edit provisioning-configuration #Add the fields provisioningDHCPRange: 172.22.0.10,172.22.0.100 provisioningIP: 172.22.0.3 provisioningNetworkCIDR: 172.22.0.0/24 #Change the privisioning network to Managed: provisioningNetwork: Managed # Use the collected boot mac addresses to replace the followings: provisioningMacAddresses: - 52:54:00:7e:e8:79 - 52:54:00:ee:e3:bc - 52:54:00:8e:a0:64 :wq 4. Verify the changes [kni@provisionhost-0-0 ~]$ oc edit provisioning-configuration Entered values are displayed in the CR [kni@provisionhost-0-0 ~]$ oc get pods -A | grep metal3 openshift-machine-api metal3-6bd5dd6f4c-tdlkd 8/8 Terminating 1 (121 ... openshift-machine-api metal3-86dccb65dd-ljwq6 10/10 Running 1 (21m The 8 pods were Terminated, 10 pods are running
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 (OpenShift Container Platform 4.9.5 bug fix 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/RHBA-2021:4005