Bug 2008096 - TestAWSFinalizerDeleteS3Bucket sometimes fails to teardown operator
Summary: TestAWSFinalizerDeleteS3Bucket sometimes fails to teardown operator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Oleg Bulatov
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-27 09:25 UTC by Oleg Bulatov
Modified: 2022-03-12 04:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-12 04:38:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 722 0 None open Bug 2008096: Fix race in TestAWSFinalizerDeleteS3Bucket 2021-09-27 09:26:25 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:38:55 UTC

Description Oleg Bulatov 2021-09-27 09:25:59 UTC
Description of problem:

The test TestAWSFinalizerDeleteS3Bucket in e2e-aws-operator sometimes files to teardown the operator.

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

4.x

How reproducible:

Often

Steps to Reproduce:
1. run tests for the operator

Actual results:

    imageregistry.go:232: uninstalling the image registry...
    imageregistry.go:122: waiting for the registry to be removed: available (False), progressing (True), Degraded (False), removed (False)
    imageregistry.go:122: waiting for the registry to be removed: available (False), progressing (True), Degraded (False), removed (False)
    imageregistry.go:122: waiting for the registry to be removed: available (False), progressing (True), Degraded (False), removed (False)
    imageregistry.go:122: waiting for the registry to be removed: available (False), progressing (True), Degraded (False), removed (False)
    imageregistry.go:122: waiting for the registry to be removed: available (True), progressing (False), Degraded (False), removed (False)

The registry were supposed to become Removed, but instead it become Available=True, Removed=False.

Expected results:

The test successfully removes all created objects.

Additional info:

Example of a failed job:

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/721/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1442266809607655424

Comment 6 errata-xmlrpc 2022-03-12 04:38:40 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.

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


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