e853bb5718
When the InstanceNUMATopology OVO has changed in I901fbd7df00e45196395ff4c69e7b8aa3359edf6 to separately track pcpus from vcpus a data migration was added. This data migration is triggered when the InstanceNUMATopology object is loaded from the instance_extra table. However that patch is missed the fact that the InstanceNUMATopology object can be loaded from the request_spec table as well. So InstanceNUMATopology object in RequestSpec are not migrated. This could lead to errors in the scheduler when such RequestSpec object is used for scheduling (e.g. during a migration of a pre Victoria instance with cpu pinning) This patch adds the missing data migration. Change-Id: I812d720555bdf008c83cae3d81541a37bd99e594 Closes-Bug: #1952941
10 lines
338 B
YAML
10 lines
338 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The `bug 1952941`_ is fixed where a pre-Victoria server with pinned
|
|
CPUs cannot be migrated or evacuated after the cloud is upgraded to
|
|
Victoria or newer as the scheduling fails with
|
|
``NotImplementedError: Cannot load 'pcpuset'`` error.
|
|
|
|
.. _bug 1952941: https://bugs.launchpad.net/nova/+bug/1952941
|