yahoo-eng-team team mailing list archive

[Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

Instance destroy and Instance snapshot are locking operations, meaning
that they can only occur sequencially. This is the result of the bugfix
for https://bugs.launchpad.net/nova/+bug/1461970 .

The problem is that the destroy instance can occur before snapshoting,
resulting in a VM NotFound exception being raised while snapshoting, as
the VM no longer exists. In the logs it can be observed that the lock
was being held by "do_terminate_instance", which was then aquired by
"instance_synchronized_snapshot".

This causes failures in some tempest tests.

Logs: http://paste.openstack.org/show/421642/

** Affects: nova
     Importance: High
     Assignee: Claudiu Belu (cbelu)
         Status: In Progress


** Tags: hyper-v

-- 
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/1486458

Title:
  Hyper-V: snapshot fails if the instance is destroyed beforehand

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Instance destroy and Instance snapshot are locking operations, meaning
  that they can only occur sequencially. This is the result of the
  bugfix for https://bugs.launchpad.net/nova/+bug/1461970 .

  The problem is that the destroy instance can occur before snapshoting,
  resulting in a VM NotFound exception being raised while snapshoting,
  as the VM no longer exists. In the logs it can be observed that the
  lock was being held by "do_terminate_instance", which was then aquired
  by "instance_synchronized_snapshot".

  This causes failures in some tempest tests.

  Logs: http://paste.openstack.org/show/421642/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1486458/+subscriptions