While I understand your concern, I think you missed the intent of
default_availability_zone
This config option is not intended for scheduling instances, but rather
for showing off by default one AZ if none exists.
With your environment, you could just decide to define any existing AZ
as default_availability_zone, this would prevent 'nova' to show off in
the AZ list.
** Changed in: nova
Status: New => 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/2018398
Title:
Wrong AZ gets showed when adding new compute node
Status in OpenStack Compute (nova):
Invalid
Bug description:
On a deployment with multi availability zones. When the operator adds
a new compute host, the service gets registered as part of
“default_availability_zone”.
This is an undesirable behavior for users as they see a new AZ
appearing which may not be related to the deployment the time window
that the host finally gets configured to its correct AZ.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2018398/+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
