Bug 2048186 - Image registry operator panics when finalizes config deletion
Summary: Image registry operator panics when finalizes config deletion
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
Depends On:
Blocks: 2048443
TreeView+ depends on / blocked
Reported: 2022-01-30 00:04 UTC by Oleg Bulatov
Modified: 2022-08-10 10:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:45:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 745 0 None open Bug 2048186: Fix panic in finalizer handler 2022-01-30 00:05:23 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:45:36 UTC

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


How reproducible:


Steps to Reproduce:
1. run the test TestAWSFinalizerDeleteS3Bucket

Actual results:

The test fails.

Expected results:

The test is green.

Additional info:

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.


Note You need to log in before you can comment on or make changes to this bug.