Bug 1916857

Summary: configs.imageregistry.operator.openshift.io cluster does not update its status fields after URL change
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, obulatov, rmarasch
Target Milestone: ---Keywords: UpcomingSprint
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Lack of update in config status during operator sync execution. Consequence: Config's status field was not presenting the most up to date (applied) swift configuration. Fix: Fixed the sync process to update config's status to config's spec values. Result: Spec and Status now are in sync with status presenting what is the current applied config.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-08 13:51:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1907202    
Bug Blocks: 1916859    

Comment 1 Wenjing Zheng 2021-01-22 09:58:32 UTC
Verified with the open pr(4.6.0-0.ci.test-2021-01-22-073453-ci-ln-7tzzcst)
if make changes on spec.storage.swift correctly, changes will be reflected in status.storage.swift; if make invalid change on spec.storage.swift, it will not be reflected.

Comment 6 errata-xmlrpc 2021-02-08 13:51:25 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 (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.