yahoo-eng-team team mailing list archive

[OpenStack Infra <1611321@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/352837
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c7af24ca8279226adc5cd8fa0984c6fd79e26d67
Submitter: Jenkins
Branch:    master

commit c7af24ca8279226adc5cd8fa0984c6fd79e26d67
Author: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
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
    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


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  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