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)
Reviewed: https:/ /review. opendev. org/c/openstack /nova/+ /820153 /opendev. org/openstack/ nova/commit/ e853bb571817217 25a89656b3cb305 8636630a6e
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit e853bb571817217 25a89656b3cb305 8636630a6e
Author: Balazs Gibizer <email address hidden>
Date: Thu Dec 2 12:52:01 2021 +0100
Migrate RequestSpec. numa_topology to use pcpuset
When the InstanceNUMATop ology OVO has changed in 0e45196395ff4c6 9e7b8aa3359edf6 to separately track ology object is loaded from the ATopology object can be loaded from the request_spec table as ology object in RequestSpec are not migrated.
I901fbd7df0
pcpus from vcpus a data migration was added. This data migration is
triggered when the InstanceNUMATop
instance_extra table. However that patch is missed the fact that the
InstanceNUM
well. So InstanceNUMATop
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: I812d720555bdf0 08c83cae3d81541 a37bd99e594
Closes-Bug: #1952941