yahoo-eng-team team mailing list archive

[Marc Koderer <m.koderer@xxxxxxxxxx>]

Setting default_schedule_zone helped. Seems I missed rebooting the nova-
api service.

But set to invalid.

** Changed in: nova
       Status: In Progress => Invalid

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

Title:
  AvailabilityZoneFilter keeps all hosts in default availability zone

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Problem:
  -----------

  If a host is part of an availability zone (AZ) it should not be part of the default availability zone.
  Otherwise scheduling hosts by default will be spread across AZs if this is not specified in
  the CLI.

  Steps to reproduce:
  --------------------------

   1.) Create AZ:
     nova aggregate-create test01 test01
   2.) Start a vm without the AZ parameter:
    nova boot "testvm" --flavor 1 --image 581a7392-587a-4eac-849d-0536243cd0b4
   3.) VM will (potentially) be started on compute node test01 even though it's not part of the default AZ

  Hints:
  ------
  If --availability-zone is not set in CLI the metadata dict will contain {.. availability-zone=None..}.

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