+++ 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): 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:
prow ci passed https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-image-registry-operator&pr=748
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. https://access.redhat.com/errata/RHSA-2022:0056