Created attachment 771096 [details] logs Description of problem: if we want to delete a volume that has snapshots we need to manually delete the snapshots before deleting the volumes. I think that the user should be given a choice if they want to either remove the volume with all its snapshots or not. Version-Release number of selected component (if applicable): openstack-cinder-2013.1.2-3.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. create a volume 2. create a snapshot from the volume 3. try to remove the volume Actual results: we will not be able to remove the volume and there is no force param to force remove volume + its snapshots Expected results: we should allow the user to remove the volume + its snapshots if they wish instead of having the user delete the snapshots manually. Additional info: [root@opens-vdsb ~(keystone_admin)]# cinder list +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ | 7b7acdc1-c1fe-4654-93f9-7c3afc03b395 | available | test | 10 | None | false | | +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ [root@opens-vdsb ~(keystone_admin)]# cinder delete 7b7acdc1-c1fe-4654-93f9-7c3afc03b395 ERROR: Invalid volume: Volume still has 1 dependent snapshots [root@opens-vdsb ~(keystone_admin)]# cinder help delete usage: cinder delete <volume> Remove a volume. Positional arguments: <volume> ID of the volume to delete.
This should probably be done by having the client perform snapshot-delete and delete volume calls.
Moving back to openstack-cinder, as a different approach has been proposed upstream.
(In reply to Eric Harney from comment #2) > Moving back to openstack-cinder, as a different approach has been proposed > upstream. Eric, any progress made upstream?
(In reply to Ayal Baron from comment #3) > Eric, any progress made upstream? No, I don't think anyone is actively pursuing this at this time.
Eric can you please check the test plan for this bug: https://tcms.engineering.redhat.com/plan/12155/openstackcinderrfesdelete-volume-with-snapshot#reviewcases and give some feedback.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Is there any chance we can re-discuss this RFE? removing a volume through an external application will make the process more complex if it will also have to remove all the redundant snapshots as well.
Can you please add a reason for the nack here?
I reopened that case for 8.0.
Moving to POST as https://review.openstack.org/#/c/201748/ was merged upstream Sean
(In reply to Sean Cohen from comment #11) This still needs code written, moving out of POST for now.
Moving to 9.0, it's not ready for 8.0.
Mitaka now supports "cinder delete --cascade" which accomplishes this.
I see the patch is merged, can we backport this to OSP 8?
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
*** This bug has been marked as a duplicate of bug 1293185 ***