yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

As discussed on IRC, the issue you mention comes from the fact that
default_schedule_zone conf flag is set to None by default.

As it's defaulted to None, then the instance has no AZ unless the user
specifically asks for one, so the AZFilter doesn't care about it.

If you want to have a default AZ for each instance, please set
default_schedule_zone to the default AZ you want (ideally, the same as
for default_availability_zone)

** 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/1451921

Title:
  live-migration fails when instance booted without specified
  availability_zone

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  If instance is booted without availability-zone parameter. It's value in instances table equal NULL.
  If live-migrate such instance, all hosts, even those, which belongs to another availability zone are correct.
  This could cause problems with attached volumes, and whole live-migration

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