Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2017429
Summary: | Objects not removed at ceph side after Pods/PV/PVC are deleted on OCP side. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Elvir Kuric <ekuric> |
Component: | ceph | Assignee: | Deepika Upadhyay <dupadhya> |
Status: | CLOSED DUPLICATE | QA Contact: | Elad <ebenahar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.9 | CC: | bniver, jdurgin, jespy, madam, mmuench, mrajanna, muagarwa, ndevos, ocs-bugs, odf-bz-bot, owasserm, sunkumar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-21 16:55:39 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: |
Comment 2
Mudit Agarwal
2021-10-27 15:29:33 UTC
Not a 4.9 blocker, moving it out. (In reply to Mudit Agarwal from comment #2) > Niels, is this another case of space reclamation problem? This could be an issue where the Ceph Mgr fails to delete an RBD-image for some reason. Unfortunately the logs of the Ceph pods are not available at this time, so confirming that is not possible. Elko, do you have a more complete must-gather that contains the Pod logs? No updates for last 4 months, please reopen if this is reproducible. This appears to be due to snapshots not being deleted at the rados level, we can reopen if it still occurs after the fix for that. *** This bug has been marked as a duplicate of bug 2067056 *** |