Comment 11 for bug 1335889

>> So, it seems the issue is related to the fact that in Nova's code we nuke the VM first and then try and delete the volumes.
>> Shouldn't nova ensure that it detaches the volume first before deleting it?

I think above behavior likely to be changed in nova considering volume muti-attach feature. So nova should detach the volume while nuking the VM and should only delete the volume if it is not attached to other live VM/s.

>> Or check the exception that comes back from the volume_api.delete call and see if it complains because it's attached, then call terminate_connection, then delete.
This lazy verification might be used to avoid some race-conditions but can have performance penalty for VM terminate operation.