yahoo-eng-team team mailing list archive

[Mauro Sergio Martins Rodrigues <maurosr@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1252177 ***
    https://bugs.launchpad.net/bugs/1252177

** This bug has been marked a duplicate of bug 1252177
   The argument availability_zone of create aggregate should be optional

-- 
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/1209007

Title:
  aggregate metadata doesn't have availability_zone key

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  The failure found in this log:
  http://logs.openstack.org/23/39723/11/check/gate-tempest-devstack-vm-
  testr-full/ea37975/console.html which was reported in bug 1208627 was
  caused by a key error raised in add_host_to_aggregate()

  The underlying error that raised the KeyError was:
  2013-08-05 18:59:04.332 18531 TRACE nova.api.openstack   File "/opt/stack/new/nova/nova/compute/api.py", line 3060, in add_host_to_aggregate
  2013-08-05 18:59:04.332 18531 TRACE nova.api.openstack     aggregate_az = aggregate_meta["availability_zone"].pop()
  2013-08-05 18:59:04.332 18531 TRACE nova.api.openstack KeyError: 'availability_zone'

  see https://review.openstack.org/#/c/40265/ log testr run n-api log:
  http://logs.openstack.org/65/40265/1/check/gate-tempest-devstack-vm-
  testr-full/58da4df/logs/screen-n-api.txt.gz

  However,  when an aggregate is created an availability_zone field is
  required. So there shouldn't be a case where there isn't an
  availability_zone key in the database. (if an aggregate isn't an
  availability_zone the key's value should be None). So there is
  probably a db race or something else going on below
  nova.compute.api.add_host_to_aggregate().

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1209007/+subscriptions