Description of problem: Registry is not available on baremetal IPI. The installer is stuck waiting on image-registry: > level=info msg="Waiting up to 1h0m0s for the cluster at https://api.ostest.test.metalkube.org:6443 to initialize..." > level=debug msg="Still waiting for the cluster to initialize: Cluster operator > image-registry has not yet reported success" > level=debug msg="Still waiting for the cluster to initialize: Cluster operator > image-registry has not yet reported success" The logs for image-registry operator say this: > E0217 20:34:34.936684 12 clusteroperator.go:94] unable to sync ClusterOperatorStatusController: storage backend not configured, requeuing > E0217 20:34:34.936831 12 controller.go:353] unable to sync: unable to get generators: storage backend not configured, requeuing Version-Release number of selected component (if applicable): 4.4.0-0.ci-2020-02-17-143917 How reproducible: Always
There may also be a secondary bug, related to this. If image-registry fails to start, the clusteroperator never gets reported. `oc get clusteroperators` is not showing image-registry at all.
In IPI installations, the registry is initially in "Removed" state. This is by design, until the user sets up persistent storage for it: https://docs.openshift.com/container-platform/4.3/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html
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:0581