Bug 1711173
| Summary: | Should gracefully exit when try to delete configs.imageregistry.operator.openshift.io | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> | |
| Component: | Image Registry | Assignee: | Corey Daley <cdaley> | |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.1.0 | CC: | adam.kaplan, aos-bugs | |
| Target Milestone: | --- | |||
| Target Release: | 4.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1737526 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-16 06:28:56 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1737526 | |||
Targeting 4.2.0. We will likely want to backport the fix to 4.1.z as well. Verified on 4.2.0-0.nightly-2019-08-01-035705: [wzheng@openshift-qe 4.2]$ oc delete configs.imageregistry.operator.openshift.io cluster config.imageregistry.operator.openshift.io "cluster" deleted [wzheng@openshift-qe 4.2]$ oc get crd | grep registry configs.imageregistry.operator.openshift.io 2019-08-01T02:46:51Z 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, 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/RHBA-2019:2922 |
Description of problem: Should not just hang there if try to delete configs.imageregistry.operator.openshift.io since bucket is not empty according to clusteroperator status. Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-16-223922 How reproducible: Always Steps to Reproduce: 1.$ oc delete configs.imageregistry.operator.openshift.io cluster 2. 3. Actual results: The command just hang there until user delete bucket in S3 console. Expected results: Should warning cannot delete since bucket is not empty. Additional info: Spec: Status: Conditions: Last Transition Time: 2019-05-17T06:52:19Z Message: The registry is ready Reason: Ready Status: True Type: Available Last Transition Time: 2019-05-17T07:05:29Z Message: The registry is being removed Reason: Removing Status: True Type: Progressing Last Transition Time: 2019-05-17T07:05:29Z Message: Unable to remove registry: unable to remove storage: BucketNotEmpty: The bucket you tried to delete is not empty status code: 409, request id: 96FCA0A86CD1C234, host id: a/AQlE2VrOtlAOoIqbZdue4iqyu01776Ceynb0yum7vHLH9ID0/l/V2ula/jranluAMv8e94d5c=, BucketNotEmpty: The bucket you tried to delete is not empty status code: 409, request id: 96FCA0A86CD1C234, host id: a/AQlE2VrOtlAOoIqbZdue4iqyu01776Ceynb0yum7vHLH9ID0/l/V2ula/jranluAMv8e94d5c= Reason: RemoveFailed Status: True Type: Degraded