Bug 2318490
| Summary: | Backingstores can not be deleted on Provider | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Filip Balák <fbalak> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Ben Eli <belimele> |
| Status: | CLOSED ERRATA | QA Contact: | Filip Balák <fbalak> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.17 | CC: | dzaken, ebenahar, kmajumde, lmauda, muagarwa, nbecker, odf-bz-bot, rohgupta |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.17.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | isf-provider | ||
| Fixed In Version: | 4.17.0-124 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-10-30 14:36:21 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 (Important: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & 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-2024:8676 |
Description of problem (please be detailed as possible and provide log snippests): If a new backingstore is created and deleted then it gets stuck with error message: The pool or resource can be deleted only by its owner or the system administrator For example: apiVersion: noobaa.io/v1alpha1 kind: BackingStore metadata: deletionTimestamp: '2024-10-11T18:00:37Z' resourceVersion: '26762499' name: pv-backingstore-80a235fca30643669e73c904 uid: f419f231-bf91-4f7d-bf8a-b9ddc55727c3 deletionGracePeriodSeconds: 0 creationTimestamp: '2024-10-11T17:55:22Z' generation: 2 managedFields: (...) namespace: openshift-storage finalizers: - noobaa.io/finalizer labels: app: noobaa spec: pvPool: numVolumes: 1 resources: requests: storage: 50Gi storageClass: ocs-storagecluster-ceph-rbd type: pv-pool status: conditions: - lastHeartbeatTime: '2024-10-14T08:08:31Z' lastTransitionTime: '2024-10-11T18:00:54Z' message: The pool or resource can be deleted only by its owner or the system administrator reason: TemporaryError status: 'False' type: Available - lastHeartbeatTime: '2024-10-14T08:08:31Z' lastTransitionTime: '2024-10-11T18:00:54Z' message: The pool or resource can be deleted only by its owner or the system administrator reason: TemporaryError status: 'True' type: Progressing - lastHeartbeatTime: '2024-10-14T08:08:31Z' lastTransitionTime: '2024-10-11T17:55:41Z' message: The pool or resource can be deleted only by its owner or the system administrator reason: TemporaryError status: 'False' type: Degraded - lastHeartbeatTime: '2024-10-14T08:08:31Z' lastTransitionTime: '2024-10-11T18:00:54Z' message: The pool or resource can be deleted only by its owner or the system administrator reason: TemporaryError status: 'False' type: Upgradeable mode: modeCode: OPTIMAL timeStamp: '2024-10-12 16:43:51.145075242 +0000 UTC m=+366948.015787081' phase: Deleting This happens on Provider mode cluster setup. Version of all relevant components (if applicable): ODF 4.17.0-117 OCP 4.17.0 Can this issue reproducible? Yes, it happens for all created backingstores. Steps to Reproduce: 1. Create a backingstore resource 2. Delete the backingstore resource Actual results: Backingstore gets created successfully but deletion is stuck with error: The pool or resource can be deleted only by its owner or the system administrator Expected results: Creation and deletion works as expected. Additional info: