We have a long standing issue about changing AZs by adding hosts to aggregates. There is a patch introducing a check that actually rejects such change https://review.opendev.org/c/openstack/nova/+/821423
I believe https://review.opendev.org/c/openstack/nova/+/821423 is the better direction. So I mark this as invalid. ** Tags added: availability-zones ** 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/1995229 Title: [Opinion] Update instance availability_zone when reset host AZ Status in OpenStack Compute (nova): Invalid Bug description: Description =========== Instance.availability_zone is set in nova.conductor while scheduling. But host's availability_zone could be modified when host is added to an aggregate, but instance.availability_zone will not be changed, instead 'availabity_zone' will be cached in applications like memcached. The issue of this strategy causes /servers/detail to cost around extra 1 second when returned list containing more than 500 servers. So my proposal is to update instance.availability_zone when host is added to a new aggregate. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1995229/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
