Reviewed: https://review.openstack.org/594050 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=690f91b5c7f7e84a4e6d351b27c05818d947cce1 Submitter: Zuul Branch: master
commit 690f91b5c7f7e84a4e6d351b27c05818d947cce1 Author: Jiří Suchomel <[email protected]> Date: Tue Aug 21 09:10:07 2018 +0200 Filter out instances without a host when populating AZ It could happen that instance does not have a host set, e.g. when its creation failed before it was scheduled. During online_migration, populate_missing_availability_zones tries to add missing AZs to all instances. However for instances without a host there's no reasonable value for AZ (we can't use a logic that bases the value on a host) so let's skip this kind of instances completely. Change-Id: Ic6060beaa08af5ea70e5e54fffb94eea58aa7bbf Closes-Bug: #1788115 ** Changed in: nova Status: In Progress => Fix Released -- 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/1788115 Title: nova-manage db online_data_migrations hangs on instances with no host set Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: In Progress Status in OpenStack Compute (nova) queens series: In Progress Status in OpenStack Compute (nova) rocky series: In Progress Bug description: When there are some deleted instances present before upgrading, "nova-manage db online_data_migrations" will not be able to finish. I think this is because populate_missing_availability_zones does not check for deleted instances (or for non-existent AZ) - so it is run over and over again because it cannot set AZ to a deleted instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1788115/+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
