-
Bug
-
Resolution: Obsolete
-
Undefined
-
None
-
4.12, 4.11
-
Critical
-
None
-
False
-
Description of problem:
When performing a Bare Metal IPI installation with the provisioning network enabled (see attached install.config.yaml), and after the masters are provisioned and the bootstrap destroyed, metal3 fails to start as the PROVISIONING_MACS env var is not filled for the containers of the metal3 deployment.This seems related to: 1. The controlplane machines kept in the provisioning state (their BMH objects have the status.state string empty) 2. The nodes don't get the providerID set 3. The cluster-baremetal-operator's [updateProvisioningMacAddresses()](https://github.com/openshift/cluster-baremetal-operator/blob/master/controllers/provisioning_controller.go#L498) method reuturns an empty list. Therefore: - The metal3 pod does not start - The workers are not provisioned - The masters Machines keep in the Provisioning state and their related BMH have no status reported - The installation fails
Version-Release number of selected component (if applicable):
registry.ci.openshift.org/ocp-arm64/release-arm64:4.11.0-0.nightly-arm64-2022-10-05-091009
How reproducible:
always
Steps to Reproduce:
1. Install an IPI baremetal cluster with the provisioning network enabled and provide the BootMACAddress for the master nodes in the install-config.yaml
Actual results:
The installation fails
Expected results:
The installation succeeds
Additional info:
See attached files and must-gather