** Description changed:

  [Impact]
  
  Affected to Xenial Mitaka, UCA Mitaka
  
  just after creating vm and state ACTIVE,
  
  When evacuating it, it is failed with ERROR state.
  
  [Test case]
  
  In below env,
  http://pastebin.ubuntu.com/25337153/
  
  Network configuration is important in this case, because I tested
  different configuration. but couldn't reproduce it.
  
- ##in progress##
+ reproduction test script ( based on juju )
  
- making detail script
+ http://pastebin.ubuntu.com/25360805/
  
  [Regression Potential]
  
  this is about evacuation, Could be issue on evacuation.
  especially recreating vm
  
  [Others]
  
  Related Patches.
  
https://github.com/openstack/nova/commit/a5b920a197c70d2ae08a1e1335d979857f923b4f
  
https://github.com/openstack/nova/commit/a2b0824aca5cb4a2ae579f625327c51ed0414d35
  
  Original description
  
  I'm working on the nova-powervm driver for Mitaka and trying to add
  support for evacuation.
  
  The problem I'm hitting is that instance.host is not updated when the
  compute driver is called to spawn the instance on the destination host.
  It is still set to the source host.  It's not until after the spawn
  completes that the compute manager updates instance.host to reflect the
  destination host.
  
  The nova-powervm driver uses instance events callback mechanism during
  plug VIF to determine when Neutron has finished provisioning the
  network.  The instance events code sends the event to instance.host and
  hence is sending the event to the source host (which is down).  This
  causes the spawn to fail and also causes weirdness when the source host
  gets the events when it's powered back up.
  
  To temporarily work around the problem, I hacked in setting
  instance.host = CONF.host; instance.save() in the compute driver but
  that's not a good solution.

** Tags added: sts-sru-needed

** Patch added: "lp1535918_xenial.debdiff"
   
https://bugs.launchpad.net/nova-powervm/+bug/1535918/+attachment/4936110/+files/lp1535918_xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535918

Title:
  instance.host not updated on evacuation

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1535918/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to