[Cinder] Odd Volume and Volume Snapshot Dependencies

Jeremy Houser jeremyhouser at protonmail.com
Fri Apr 12 19:44:15 UTC 2019

Currently running python-openstackclient functional tests against an
openstack deployment. Ran into some odd functionality whilst
manipulating volumes and snapshots in openstack via cli and gui.

I create a volume, create a snapshot of that volume, and then create a
volume from that snapshot. I can't delete the snapshot until I delete the
volume that I spawned using that snapshot. I understand the dependency
of "can't delete a volume while a snapshot dependent on that volume is
deleted first" but why can't a volume snapshot be deleted when volumes
are spawned from it? Is this intentional? I am working with Cinder 3.27.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190412/a85094cc/attachment.html>

More information about the openstack-discuss mailing list