Description of problem: IHAC recently deployed OCP 4.3 on vsphere and see the following message with the image-registry while they apply the patch mentioned for non-production cluster, ~~~ E0204 12:36:16.365396 13 controller.go:257] unable to sync: unable to finalize resource: storage backend not configured, requeuing I0204 12:36:16.365471 13 finalizer.go:40] finalizing *v1.Config, Name=cluster I0204 12:36:17.358735 13 generator.go:340] object *v1.ClusterOperator, Name=image-registry updated: changed:metadata.resourceVersion={"8651327" -> "8651341"}, changed:metadata.selfLink={"/apis/config.openshift.io/v1/clusteroperators/image-registry" -> "/apis/config.openshift.io/v1/clusteroperators/image-registry/status"}, changed:status.conditions.0.lastTransitionTime={"2020-02-04T12:36:15Z" -> "2020-02-04T12:36:16Z"}, changed:status.conditions.2.lastTransitionTime={"2020-02-04T12:36:16Z" -> "2020-02-04T12:36:17Z"} E0204 12:36:17.359035 13 controller.go:257] unable to sync: unable to finalize resource: storage backend not configured, requeuing ~~~ $ oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"storage":{"emptyDir":{}}}}' The latest must-gather from the cluster is included as well. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: The image-regsitry cluster operator is in Degraded state and the status section for the 'configs.imageregistry.operator.io' is not getting updated. Expected results: Additional info:
Jatan, when the operator detects that it doesn't have the config resource, it runs Bootstrap() [1]. [1]: https://github.com/openshift/cluster-image-registry-operator/blob/0ba502438b44e663ae5adbacf0b4eb2bfd41aac0/pkg/operator/bootstrap.go#L33
Moving this ticket to version 4.5. We gonna need to create other tickets to back port the solution.
Verified on 4.5.0-0.nightly-2020-03-30-203132: 1. On an UPI cluster, remove config: $oc delete crd configs.imageregistry.operator.openshift.io 2. Check image registry pod is gone and no below log in operator log: "unable to sync: unable to get generators: storage backend not configured, requeuing"
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:2409