At the moment, the instance snapshot operation is synchronized using
the instance uuid. This was added some time ago, as the instance
destroy operation was failing when an instance snapshot was in
proggress.
This is now causing a deadlock, as a similar lock was recently
introduced in the manager for the shelve operation by this change:
Id36b3b9516d72d28519c18c38d98b646b47d288d
We can safely remove the lock from the HyperV driver as we now stop
pending jobs when destroying instances.
Closes-Bug: #1611321
Change-Id: I1c2ca0d24c195ebaba442bbb7091dcecc0a7e781
(cherry picked from commit e4208017feb92de8bfbe1c3b28d6b6e3cea7ab2c)
Reviewed: https:/ /review. openstack. org/375601 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=590e678fcf4 fc8eaabf2af51fa 3b76a137adbd61
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 590e678fcf4fc8e aabf2af51fa3b76 a137adbd61
Author: Lucian Petrut <email address hidden>
Date: Tue Aug 9 13:37:01 2016 +0300
HyperV: remove instance snapshot lock
At the moment, the instance snapshot operation is synchronized using
the instance uuid. This was added some time ago, as the instance
destroy operation was failing when an instance snapshot was in
proggress.
This is now causing a deadlock, as a similar lock was recently d72d28519c18c38 d98b646b47d288d
introduced in the manager for the shelve operation by this change:
Id36b3b9516
We can safely remove the lock from the HyperV driver as we now stop
pending jobs when destroying instances.
Closes-Bug: #1611321
Change-Id: I1c2ca0d24c195e baba442bbb7091d cecc0a7e781 8bfbe1c3b28d6b6 e3cea7ab2c)
(cherry picked from commit e4208017feb92de