yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Found it, this was the change, https://review.openstack.org/#/c/446053/,
in Pike.

I'm not sure what to do here, I guess if the
instance.get('availability_zone') returns None, we have to fallback to
trying to do the up-call.

** Summary changed:

- Old instances can get AVZ from metadata
+ metadata-api fails to get availability zone for instances created before pike

** Changed in: nova
       Status: New => Triaged

** Changed in: nova
   Importance: Undecided => High

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Changed in: nova/pike
       Status: New => Triaged

** Changed in: nova/queens
       Status: New => Triaged

** Changed in: nova/pike
   Importance: Undecided => High

** Changed in: nova/queens
   Importance: Undecided => High

-- 
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):
  Triaged
Status in OpenStack Compute (nova) pike series:
  Triaged
Status in OpenStack Compute (nova) queens series:
  Triaged

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