** Changed in: cloud-archive Status: New => 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/1535918
Title: instance.host not updated on evacuation Status in Ubuntu Cloud Archive: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in nova package in Ubuntu: New Bug description: [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. reproduction test script ( based on juju ) http://pastebin.ubuntu.com/25360805/ [Regression Potential] this is about evacuation, Could be issue on evacuation. especially recreating vm [Others] In test, I should patch two commits, one from https://bugs.launchpad.net/nova/+bug/1686041 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. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1535918/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp