← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1555699] Re: Hyper-V: failed cold migrations cannot be reverted

 

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

commit 9740e18a31c0682d2852ac745242c69475d89113
Author: Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Fri Mar 11 16:09:52 2016 +0200

    hyper-v: Copies back files on failed migration
    
    On cold migration, the contents of the instance folder are
    copied to the new host. The original folder cannot be removed
    because the VM configuration files cannot be deleted until the VM
    is destroyed.
    
    Because of this, when the migration fails to copy the files, it will
    try to revert this through folder renaming. Since the original folder
    still exists, an exception is raised.
    
    Change-Id: Ia42ed873924999d57336a105bcaa2b856f3a3a9d
    Closes-Bug: #1555699


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

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

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

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


References