Description of problem: Upgrading a cluster from 4.1->4.2 fails, the image-registry operator never upgrades and instead reports: E0707 10:56:14.395648 1 controller.go:278] unable to sync: unable to apply objects: failed to update object *v1.Deployment, Namespace=openshift-image-registry, Name=image-registry: unable to get cluster proxy configuration: proxy.config.openshift.io "cluster" not found, requeuing Version-Release number of selected component (if applicable): 4.2 (upgraded from 4.1) Cluster Image Registry Operator Version: 4.0.0-229-g7833ddc-dirty How reproducible: always Steps to Reproduce: 1. install 4.1 cluster 2. upgrade to latest 4.2 Additional info: There was an attempt to fix this here: https://github.com/openshift/cluster-image-registry-operator/pull/309 but it's still failing in this job which used the latest code: https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2/156 registry operator logs are here: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2/156/artifacts/e2e-aws-upgrade/pods/openshift-image-registry_cluster-image-registry-operator-79684bdcd9-tzr9w_cluster-image-registry-operator.log
Submitted pull request https://github.com/openshift/cluster-image-registry-operator/pull/315 which will just throw a warning into the logs if the proxy configuration does not exist, instead of returning an error.
https://github.com/openshift/cluster-image-registry-operator/pull/316 has merged. Hopefully it will take care of this issue.
Looks like we are back to green: https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2/158/
This bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1733015.
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-2019:2922