From what I can observe from the logs, failing to destroy in instance consistently appears after performing the snapshot operation. The reason why it fails to destroy the instance is because a request to destroy it has been received before the snapshoting completed and there is no locking mechanisms between operations (ideal for race conditions). This can be a problem with any long-lasting tasks such as this. I think this will have to be investigated further. Maybe other drivers are affected as well?
Hello Matt. Thanks for reporting this bug, but as it currently stands, this is a duplicate of bug: https:/ /bugs.launchpad .net/nova/ +bug/1461970
From what I can observe from the logs, failing to destroy in instance consistently appears after performing the snapshot operation. The reason why it fails to destroy the instance is because a request to destroy it has been received before the snapshoting completed and there is no locking mechanisms between operations (ideal for race conditions). This can be a problem with any long-lasting tasks such as this. I think this will have to be investigated further. Maybe other drivers are affected as well?
A fix is attempted for the mentioned bug.