This is actually invalid, failure during spawn should actually result in the volume remaining attached and in-use as happens now. We could call _disconnect_volume when we hit an error during attach_encryptor but I believe we should also clean this up when the instance is destroyed anyway.
This is actually invalid, failure during spawn should actually result in the volume remaining attached and in-use as happens now. We could call _disconnect_volume when we hit an error during attach_encryptor but I believe we should also clean this up when the instance is destroyed anyway.