Cloned from launchpad bug 1370390.
When we resize (change the flavor) of an instance that has a NUMA topology defined, the NUMA info from the new flavor will not be considered during scheduling. The instance will get re-scheduled based on the old NUMA information, but the claiming on the host will use the new flavor data. Once the instane sucessfully lands on a host, we will still use the old data when provisioning it on the new host.
We should be considering only the new flavor information in resizes.
Specification URL (additional information):
Product Management has reviewed and declined this request.
You may appeal this decision by reopening this request.