Reviewed: https://review.openstack.org/567878
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6b4c38c04177ff194d05368cd4aff69958075167
Submitter: Zuul
Branch: master
commit 6b4c38c04177ff194d05368cd4aff69958075167
Author: Surya Seetharaman <suryaseetharama...@gmail.com>
Date: Fri May 11 17:12:34 2018 +0200
Metadata-API fails to retrieve avz for instances created before Pike
In Pike (through change: I8d426f2635232ffc4b510548a905794ca88d7f99)
we started setting instance.avilability_zone during schedule time by
calculating the avz of the host into which the instance was scheduled
into. After this change was introduced, the metadata request for the avz
on the instance (through change: I73c3b10e52ab4cfda9dacc0c0ba92d1fcb60bcc9)
started using instance.get(availability_zone) instead of doing the upcall.
However this would return None for instances older than Pike whose
availability_zone was not mentioned during boot time as it would be set to
CONF.default_schedule_zone whose default value is None.
This patch adds an online_migration tool to populate missing
instance.availability_zone values.
Change-Id: I2a1d81bfeb1ea006c16d8f403e045e9acedcbe57
Closes-Bug: #1768876
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova/pike
Status: Triaged => In Progress
** Changed in: nova/pike
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
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/1768876
Title:
metadata-api fails to get availability zone for instances created
before pike
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) pike series:
In Progress
Status in OpenStack Compute (nova) queens series:
In Progress
Bug description:
Can't get AVZ for old instances:
curl http://169.254.169.254/latest/meta-data/placement/availability-zone
None#
This is because the upcall to the nova_api DB was removed in the commit:
9f7bac2
and old instances may haven't the AVZ defined.
Previously, the AVZ in the instance was only set if explicitly defined by the
user.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1768876/+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
