Public bug reported:
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.
** Affects: compute-hyperv
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Tags: hyper-v
** Also affects: compute-hyperv
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1611321
Title:
HyperV: shelve vm deadlock
Status in compute-hyperv:
New
Status in OpenStack Compute (nova):
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1611321/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
