Bug 2117852 - Unable to delete cinder volumes and snapshots
Summary: Unable to delete cinder volumes and snapshots
Keywords:
Status: CLOSED DUPLICATE of bug 2039274
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 16.2 (Train)
Hardware: x86_64
OS: Other
medium
medium
Target Milestone: ---
: ---
Assignee: Cinder Bugs List
QA Contact: Tzach Shefi
Andy Stillman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-12 07:19 UTC by vivek koul
Modified: 2022-09-23 03:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-23 03:44:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1989680 0 medium CLOSED RBD Volume can't be removed if other volumes were created from a snapshot of this volume and were not removed 2024-04-25 06:39:23 UTC
Red Hat Issue Tracker OSP-18175 0 None None None 2022-08-12 07:25:32 UTC

Description vivek koul 2022-08-12 07:19:09 UTC 
Description of problem:

Customer is trying to delete the volumes/snapshot. But it is failing because the customer has already deleted it from ceph side manually.

Now we have stale entries left in openstack DB.

Need help with clearing up the stale entries left in DB.

Version-Release number of selected component (if applicable):
cat /etc/rhosp-release 
Red Hat OpenStack Platform release 16.2 (Train)

cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.4 (Ootpa)

How reproducible:
Delete the volume manually from ceph side and then try to delete it from openstack side.

Steps to Reproduce:
1. Delete the volume manually from ceph side and then try to delete it from openstack side.
2.
3.

Actual results:
Not able to delete snapshots and volumes

Expected results:
Clear the stale entries.

Additional info:
This is upstream ceph.
Comment 5 Eric Harney 2022-08-23 14:10:11 UTC 
This is likely another manifestation of bug 1989680.
Note You need to log in before you can comment on or make changes to this bug.