Bug 1791829 - [OSP13][cinder] Connot delete snapshot after an instance was spawned from it and then deleted
Summary: [OSP13][cinder] Connot delete snapshot after an instance was spawned from it ...
Keywords:
Status: CLOSED DUPLICATE of bug 1870282
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jon Bernard
QA Contact: Tzach Shefi
Chuck Copello
URL:
Whiteboard:
Depends On: 1703939 1777781
Blocks: 1795959
TreeView+ depends on / blocked
 
Reported: 2020-01-16 14:57 UTC by Sofia Enriquez
Modified: 2023-10-25 11:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1777781
: 1795959 (view as bug list)
Environment:
Last Closed: 2021-04-01 09:51:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-1720 0 None None None 2023-10-25 06:13:36 UTC

Comment 5 Sofia Enriquez 2020-01-29 16:42:22 UTC 
An image is created from an instance booted from a volume, then a vm is spawned from that image.
Even if the instance is deleted the snapshot cannot be deleted anymore. 

Version-Release number of selected component (if applicable):
RHOSP 14z3

How reproducible:
always

Steps to Reproduce:
 1. Boot instance from image and create boot volume
 2. Create image from the the instance
 3. Create a second instance from the new image
 4, Delete the instance just created
 5, Try to delete the snapshot

Expected Result:
Should delete the snapshot

Actual Result:
It fails with the following error:
2019-11-28 10:21:26.210 63 ERROR cinder.volume.manager [default default] Delete snapshot failed, due to snapshot busy.: SnapshotIsBusy: deleting snapshot snapshot-c-45ae that has dependent volumes
Comment 15 Luigi Toscano 2021-04-01 09:51:50 UTC 
This is going to be addressed in OSP 16.2 thanks to the usage of RBD Clone v2 API. Please see bug 1764324.
As this is bug is a specifically targeted to OSP13, I'm going to close it as duplicate of bug 1870282, which was meant to find a solution on OSP13 but it is not going to be implemented in the end.

*** This bug has been marked as a duplicate of bug 1870282 ***
Note You need to log in before you can comment on or make changes to this bug.