the problem it that cinder does not _show_ snapshots if volumes list or volume details is called. Cinder doesn't allow do delete volume if it has snapshot. It's a common behavior to not delete objects if it contains depended data. Volumes could be deleted only if all it's snapshots are deleted.
We can't fix it in MOS <7 because it requires API changes. It could be REST API or python-cinderclient API. In such cases our OpenStack will have different API with upstream.
I can't say that it is workaround, because it's a feature request, not bug. May be it's only UX issue.
you need to call 'cinder snapshot-list | grep <vol_id>' before volume delete and delete all volume's snapshots using 'cinder snapshot-delete <snapshot_id>' command
Dmitry B,
the problem it that cinder does not _show_ snapshots if volumes list or volume details is called. Cinder doesn't allow do delete volume if it has snapshot. It's a common behavior to not delete objects if it contains depended data. Volumes could be deleted only if all it's snapshots are deleted.
We can't fix it in MOS <7 because it requires API changes. It could be REST API or python-cinderclient API. In such cases our OpenStack will have different API with upstream.
I can't say that it is workaround, because it's a feature request, not bug. May be it's only UX issue.
you need to call 'cinder snapshot-list | grep <vol_id>' before volume delete and delete all volume's snapshots using 'cinder snapshot-delete <snapshot_id>' command