Wrong AZ gets showed when adding new compute node

[Sahid Orentino]

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.

[Sylvain Bauza (sylvain-bauza)]

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.

[Sylvain Bauza (sylvain-bauza)]

Marking the bug as Invalid, but feel free to reopen it if you have concerns by what I replied.