yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

When performing a cold migration, the Hyper-V driver moves the instance
files to a temporary folder, and from there, it copies them to the
destination node.

The instance folder is not moved entirely, as it will hold some Hyper-V
specific files that cannot be deleted/moved while the instance exists,
basically we just take the files that we care about, while leaving the
folder there.

If the migration fails, the driver tries to move the temporary directory
to the actual instance path, but fails as there already is a folder.

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

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

Title:
  Hyper-V: failed cold migrations cannot be reverted

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

Bug description:
  When performing a cold migration, the Hyper-V driver moves the
  instance files to a temporary folder, and from there, it copies them
  to the destination node.

  The instance folder is not moved entirely, as it will hold some
  Hyper-V specific files that cannot be deleted/moved while the instance
  exists, basically we just take the files that we care about, while
  leaving the folder there.

  If the migration fails, the driver tries to move the temporary
  directory to the actual instance path, but fails as there already is a
  folder.

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

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