Resize instace will not change the NUMA topology of a running instance to the one from the new flavor
Bug #1370390 reported by
Nikola Đipanov
This bug affects 11 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Stephen Finucane |
Bug Description
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.
Changed in nova: | |
status: | New → Confirmed |
importance: | High → Medium |
Changed in nova: | |
assignee: | nobody → Tiago Rodrigues de Mello (timello) |
Changed in nova: | |
assignee: | Nikola Đipanov (ndipanov) → Ed Leafe (ed-leafe) |
Changed in nova: | |
status: | In Progress → Invalid |
To post a comment you must log in.
This bug essentially means that resize is not usable for any instances that have a NUMA topology. Is anyone working on this?