Bug 2048443 - 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.10.0
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
Depends On: 2048186
TreeView+ depends on / blocked
Reported: 2022-01-31 09:30 UTC by OpenShift BugZilla Robot
Modified: 2022-03-10 16:43 UTC (History)
1 user (show)

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.
Clone Of:
Last Closed: 2022-03-10 16:42:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 748 0 None open [release-4.10] Bug 2048443: Fix panic in finalizer handler 2022-01-31 09:30:54 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:43:08 UTC

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.


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