[Cinder] Odd Volume and Volume Snapshot Dependencies
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...