Bug 1972190
| Summary: | Attempt to remove pv-pool based noobaa-default-backing-store fails and makes this pool stuck in Rejected state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Martin Bukatovic <mbukatov> | ||||
| Component: | Multi-Cloud Object Gateway | Assignee: | Kfir Payne <kfpayne> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Bukatovic <mbukatov> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | etamir, kramdoss, muagarwa, nbecker, nberry, ocs-bugs, odf-bz-bot, rcyriac | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened | ||||
| Target Release: | ODF 4.10.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 4.10.0-79 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-04-13 18:49:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Martin Bukatovic
2021-06-15 12:07:40 UTC
Fixing state of this bug: - dropping "CLI only" from the title, I must have overlooked that when cloning - moving it back to NEW, if we want to declare it as RFE and not track it in bugzilla, we would need to open a JIRA for the feature (that said, I'm not fully convinced that this is "a feature") This is not an RFE, but a bug which depends on a feature which is not yet present. Let's keep it open, and for better tracking, mark the validation feature as a blocker for this bug. Hi Martin, Few questions: - Is it reproducible? - I see OCS 4.5. do we see it on later versions too? - Any workaround available? - In the last comment you are saying that it depends on a feature that is not yet present - what is that feature? - Is this scenario was tested as part of a feature for 4.8 release? Thanks (In reply to Raz Tamir from comment #10) > - Is it reproducible? Yes, but I haven't tried it since I stopped working on this and don't plan to retry. > - I see OCS 4.5. do we see it on later versions too? I assume yes. I haven't tried myself. > - Any workaround available? I'm not aware of any workaround. > - In the last comment you are saying that it depends on a feature that is > not yet present - what is that feature? I don't know myself as well. You would need to ask Eran or Nimrod. > - Is this scenario was tested as part of a feature for 4.8 release? No. The main problem here is that original BZ 1876633 was mishandled by development team, which wastes time for everyone. See: https://bugzilla.redhat.com/show_bug.cgi?id=1876633#c28 Testing with GCP cluster: OCP 4.10.0-0.nightly-2022-02-15-041303 ODF 4.10.0-156 And I see that when one attempts to delete `backingstore/noobaa-default-backing-store`, the action is rejected: ``` $ oc delete backingstore/noobaa-default-backing-store -n openshift-storage Error from server: admission webhook "admissionwebhook.noobaa.io" denied the request: cannot complete because pool "noobaa-default-backing-store" in "IN_USE" state ``` The same applies to the attempt to remove the backing store via OCP Console, which reports: ``` An error occurred admission webhook "admissionwebhook.noobaa.io" denied the request: cannot complete because pool "noobaa-default-backing-store" in "IN_USE" state ``` Created attachment 1861440 [details]
verification screenshot: removal of backingstore/noobaa-default-backing-store is rejected
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 (Important: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & bug fix 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:1372 |