yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1582543@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

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

Title:
  Pre  live-migration failed  cannot rollback  source connection
  information

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description:
  Boot vm from volume, if when pre_live_migration, the bdm connection_info has been updatated as the dest connection_info. So, if pre_live_migration failed, the _rollback_live_migration should be updated
  the source host connection_info to bdm table. Otherwise, the virtual machine migration failure can not work properly.
  Steps to reproduce:
  1. Boot vm from volume
  2. Construction of pre migration failed.
  3. Run nova live-migration vm
  4. The vm looks like good, But if you hard reboot the vm, the vm will be anomaly.

  Expected result:
  After vm live-migration failed, the vm can be ok.

  Actual result:
  As for the vm bdm connection_info was updated to the dest information. But the virsh process was still in source host. So, the vm's hard-reboot,stop,start actions are not ok.

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