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 c7af24ca8279226adc5cd8fa0984c6fd79e26d67)
Reviewed: https:/ /review. openstack. org/357566 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=8f20e7067fb d2c784cd65876f5 8dd3cde59f966c
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 8f20e7067fbd2c7 84cd65876f58dd3 cde59f966c
Author: Lucian Petrut <email address hidden>
Date: Tue Aug 9 13:21:48 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 adc5cd8fa0984c6 fd79e26d67)
(cherry picked from commit c7af24ca8279226