Description of problem: We you decide to change your storage (for example, from S3 to PVC), the information about the old storage doesn't get evicted from the config.imageregistry.operator.openshift.io Status field. As a result, finalization of the config resource fails because it sees two configurations. Steps to Reproduce: 1. Create a cluster on S3. 2. Wait until the image registry gets deployed. 3. oc edit config.imageregistry.operator.openshift.io: change spec.storage so that it uses another storage 4. oc delete config.imageregistry.operator.openshift.io Actual results: The resource cannot be deleted. Expected results: The resource is deleted.
Could reproduce this in 4.2 version 4.2.0-0.nightly-2019-10-11-230724 Verified in 4.3.0-0.nightly-2019-10-15-180816. Steps: 1. Create a cluster based on aws platfrom which used s3 storage default. 2. Wait until the image registry gets deployed. 3. oc edit config.imageregistry.operator.openshift.io: change spec.storage to use pvc. 4. Check config.imageregistry again, the status.storage only have one method storage. 5. Delete config.imageregistry, it can be deleted quickly.
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:0062