Bug 1759159

Summary: [4.2.z] Changing storage type makes impossible to delete config.imageregistry.operator.openshift.io
Product: OpenShift Container Platform Reporter: Oleg Bulatov <obulatov>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: adam.kaplan, aos-bugs, wzheng, xiuwang
Target Milestone: ---   
Target Release: 4.2.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1722878 Environment:
Last Closed: 2019-10-30 04:44:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1722878    
Bug Blocks:    

Comment 2 XiuJuan Wang 2019-10-24 01:53:28 UTC 
Verified in 4.2.0-0.nightly-2019-10-23-123520.
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.
Comment 4 errata-xmlrpc 2019-10-30 04:44:56 UTC 
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:3151