yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

We create a planned vm during live migration when having passthrough
disks attached in order to properly configure the resources of the 'new'
instance.

The issue is that if the migration fails, this planned vm is not cleaned
up.

Although planned vms are destroyed at a second attempt to migrate the
instance, this issue had an impact on the Hyper-V CI as planned vms
persisted among CI runs and vms having the same name failed to spawn, as
there were file handles kept open by the VMMS service, preventing the
instance path from being cleaned up.

Trace:
http://paste.openstack.org/show/536149/

** Affects: compute-hyperv
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** 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/1604078

Title:
  Hyper-V: planned vms are not cleaned up

Status in compute-hyperv:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  We create a planned vm during live migration when having passthrough
  disks attached in order to properly configure the resources of the
  'new' instance.

  The issue is that if the migration fails, this planned vm is not
  cleaned up.

  Although planned vms are destroyed at a second attempt to migrate the
  instance, this issue had an impact on the Hyper-V CI as planned vms
  persisted among CI runs and vms having the same name failed to spawn,
  as there were file handles kept open by the VMMS service, preventing
  the instance path from being cleaned up.

  Trace:
  http://paste.openstack.org/show/536149/

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1604078/+subscriptions