yahoo-eng-team team mailing list archive

[WeiguoFan <wei-fan@xxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1535918 ***
    https://bugs.launchpad.net/bugs/1535918

** This bug has been marked a duplicate of bug 1535918
   instance.host not updated on evacuation

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

Title:
  Vif-plug event was been sent to old node cause evacuating failed

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Description
  ===========
  When using host-evacuate command, some vms on failed host would be failed when evacuating because
  the vif-plug event was be sent to failed node not the node which vm launched on.

  Steps to reproduce
  ==================
  1.create 8 vms on host1

  2.nova service-force-down host1 nova-compute
    nova service-force-down host1 nova-conductor
    nova service-force-down host1 nova-scheduler

  3.evacuate the vms on host1
    nova  host-evacuate host1

  Expected result
  ===============
  After the execution of the steps above, all of vms on hosts1 should be evacuated to other hosts

  
  Actual result
  =============
  only 2-3 vms can be evacuated, others became to failed

  Environment
  ===========
  1. My openstack version is mitaka

  2. Use Libvirt + Kvm in OpenStack

  2. Use Ceph as backend storage

  3. Use Neutron with OpenVSwitch

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