Comment 8 for bug 1550180

We have seen this problem as well in Queens release. Our VMs write huge data to cinder Volumes (/dev/vdb) all the time.
At this point of time if we run "stack delete", it results exactly the same failure.

This problem subsides if we first shutdown the VMs before stack delete. Should this be somehow incorporated in the heat code itself?

(Or)
Should heat simply delete the libvirt VM domain without trying to detach the volume?