** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => Triaged
** Changed in: nova/queens
Status: New => Triaged
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/rocky
Status: New => Triaged
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova/rocky
Importance: Undecided => Medium
--
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):
In Progress
Status in OpenStack Compute (nova) pike series:
Triaged
Status in OpenStack Compute (nova) queens series:
Triaged
Status in OpenStack Compute (nova) rocky series:
Triaged
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 : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
