yahoo-eng-team team mailing list archive

[Eli Qiao <liyong.qiao@xxxxxxxxx>]

another blue print is working on
https://blueprints.launchpad.net/nova/+spec/manager-restart-during-
migration

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

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

Title:
  instance 's host was not updated after live-migration if source
  compute host crash

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  I do a live-migration from host1 to host2
  live-migration successfully to but the instance's host is not set back to host2 yet before host1's nova-compute service crash(ctrl+c to stop it)

  nova list show that the instance is still active(actually , it is done
  the migration and I can see it host2 by virsh list)

  taget@liyong:~/devstack$ nova list
  +--------------------------------------+-------+--------+------------+-------------+----------------------+
  | ID                                   | Name  | Status | Task State | Power State | Networks             |
  +--------------------------------------+-------+--------+------------+-------------+----------------------+
  | 1d114104-9a62-49ba-b209-6a42beff4133 | test1 | ACTIVE | -          | NOSTATE     | private_net=10.0.0.9 |

  show this instance, the instance's host is still host1(due to host1's
  compute crashed an no chance to set it yet).

  after that. do a reboot on this instance, failed due to the instance
  can not be found from host1 host(yes, it is)

  and nova set it to error status(but the instance is still running on
  host2)

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