Description of problem: On a compact 3 x masters cluster after the installation succeeded baremetal operators reports Progressing status with 'Applying metal3 resources' message Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2021-12-21-130047 How reproducible: 100% Steps to Reproduce: 1. Deploy a 3 x masters IPv6 compact cluster with disabled provisioning network 2. Wait for deployment to succeed 3. oc get clusteroperators baremetal Actual results: AME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE baremetal 4.10.0-0.nightly-2021-12-21-130047 True True False 19h Applying metal3 resources status conditions: Conditions: Last Transition Time: 2021-12-21T18:07:56Z Message: Applying metal3 resources Reason: SyncingResources Status: True Type: Progressing Expected results: operator reports progressing false Additional info: Attaching must-gather
Looking at the logs it appears that the image-customization-controller deployment is not coming up due to : 2021-12-21T18:07:59.206806724Z E1221 18:07:59.206746 1 controller.go:317] controller/provisioning "msg"="Reconciler error" "error"="unable to determine Ironic's IP to pass to the image-customization-controller: pods is forbidden: User \"system:serviceaccount:openshift-machine-api:cluster-baremetal-operator\" cannot list resource \"pods\" in API group \"\" in the namespace \"openshift-machine-api\"" "name"="provisioning-configuration" "namespace"="" "reconciler group"="metal3.io" "reconciler kind"="Provisioning"
*** This bug has been marked as a duplicate of bug 2035239 ***