Reviewed: https://review.openstack.org/567701 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0ed68c76fa8a84d1d5f0ab945e34c8e16341d627 Submitter: Zuul Branch: master
commit 0ed68c76fa8a84d1d5f0ab945e34c8e16341d627 Author: Matt Riedemann <[email protected]> Date: Thu May 10 19:27:36 2018 -0400 Update instance.availability_zone during live migration While triaging bug 1768876 there was some concern that change I8d426f2635232ffc4b510548a905794ca88d7f99 in Pike had regressed some behavior where a user that does not explicitly request a specific AZ during server create is then later restricted to only move operations within that same AZ. This test shows that is not a regression because the AvailabilityZoneFilter looks at RequestSpec.availability_zone rather than instance.availabililty_zone, so the instance is free to be moved across zones. As a result of the test, however, it was noticed that the instance.availability_zone isn't updated during live migration once the destination host is selected. The other move operations like unshelve, evacuate and cold migrate all update the instance.availabiltiy_zone, so this copies the same logic. Change-Id: I9f73c237923fdcbf4096edc5aedd2c968d4b893e Closes-Bug: #1771860 Related-Bug: #1768876 ** Changed in: nova Status: In Progress => 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/1771860 Title: instance.availability_zone reports wrong az after live migration Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: Triaged Status in OpenStack Compute (nova) queens series: Triaged Status in OpenStack Compute (nova) rocky series: In Progress Bug description: This is a follow up to bug 1768876 and was discovered via functional testing for that bug here: https://review.openstack.org/#/c/567701/ The scenario is: 1. create two compute hosts in separate AZs (zone1 and zone2) 2. create an instance without specifying an AZ so it can move freely between hosts in different zones 3. live migrate the instance - since there is only one other host, the instance has to move to the other zone 4. assert the instance.availability_zone is updated to reflect the other zone #4 fails because the live migration conductor task doesn't update the instance.az once a destination host is picked by the scheduler. Note that the other move operations like unshelve, evacuate and cold migrate do update the instance.az once a host is picked. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1771860/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
