Bug 2048186

Summary:	Image registry operator panics when finalizes config deletion
Product:	OpenShift Container Platform	Reporter:	Oleg Bulatov <obulatov>
Component:	Image Registry	Assignee:	Oleg Bulatov <obulatov>
Status:	CLOSED ERRATA	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 10:45:08 UTC	Type:	Bug
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:
Bug Blocks:	2048443

Description Oleg Bulatov 2022-01-30 00:04:07 UTC

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):

4.x

How reproducible:

Sometimes

Steps to Reproduce:
1. run the test TestAWSFinalizerDeleteS3Bucket

Actual results:

The test fails.

Expected results:

The test is green.

Additional info:

Comment 3 XiuJuan Wang 2022-02-07 04:03:01 UTC

prow ci passed, https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-image-registry-operator&pr=745

Comment 5 errata-xmlrpc 2022-08-10 10:45:08 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.11.0 bug fix and 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.

https://access.redhat.com/errata/RHSA-2022:5069