Bug 2048443

Summary: Image registry operator panics when finalizes config deletion
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: XiuJuan Wang <xiuwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: aos-bugs
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: the registry operator were re-getting the config object on conflict, but it were getting it into a new local scoped variable. Consequence: the new local scoped were hiding another variable that should've get this config. Fix: eliminate creation of the local scoped variable and put the config into the correct one. Result: the config is stored in the right variable and the operator doesn't panic.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:42:51 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: 2048186    
Bug Blocks:    

Description OpenShift BugZilla Robot 2022-01-31 09:30:43 UTC
+++ This bug was initially created as a clone of Bug #2048186 +++

Description of problem:

The test TestAWSFinalizerDeleteS3Bucket often fails with messages like

waiting for the registry: generation=3, observedGeneration=2
failed to wait for the imageregistry resource to be processed: timed out waiting for the condition

That's because the operator panics and with the new leader election it needs several minutes to recover.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. run the test TestAWSFinalizerDeleteS3Bucket

Actual results:

The test fails.

Expected results:

The test is green.

Additional info:

Comment 6 errata-xmlrpc 2022-03-10 16:42:51 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 (Moderate: OpenShift Container Platform 4.10.3 security 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.