Bug 2008096
| Summary: | TestAWSFinalizerDeleteS3Bucket sometimes fails to teardown operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Oleg Bulatov <obulatov> |
| Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.6 | CC: | aos-bugs |
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-12 04:38:40 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: | |||
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 |
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