yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95553
[Bug 2103636] [NEW] Live Migration Fails for Flavor-Based Requests with NUMA Constraints Due to Redundant PCI Check
Public bug reported:
A bug occurs when a user requests a live migration with a flavor-based
request that includes NUMA constraints (e.g., CPU affinity). The
migration process hits the _test_pci() method, which incorrectly
enforces a restriction allowing only port-based requests, causing the
migration to fail unnecessarily.
Expected Behavior:
Live migration should succeed for flavor-based requests with NUMA
constraints, as these are now supported.
Actual Behavior:
Live migration fails due to the _test_pci() method, which wrongly
rejects flavor-based requests under the assumption that only port-based
requests are valid.
Steps to Reproduce:
Create an instance with a flavor-based request that includes NUMA constraints (e.g., CPU affinity).
Initiate a live migration.
Observe that the migration fails at the _test_pci() method due to an unnecessary restriction.
Root Cause:
The _test_pci() check is redundant as a similar verification is already performed earlier in the migration process.
The check incorrectly assumes that only port-based requests should pass, while flavor-based requests should also be allowed.
Proposed Fix:
Remove the _test_pci() method, as it is no longer necessary.
Ensure that functional tests cover mixed-mode scenarios (port-based + flavor-based requests) to prevent regressions.
** Affects: nova
Importance: High
Assignee: Uggla (rene-ribaud)
Status: Confirmed
** Changed in: nova
Status: New => Confirmed
--
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/2103636
Title:
Live Migration Fails for Flavor-Based Requests with NUMA Constraints
Due to Redundant PCI Check
Status in OpenStack Compute (nova):
Confirmed
Bug description:
A bug occurs when a user requests a live migration with a flavor-based
request that includes NUMA constraints (e.g., CPU affinity). The
migration process hits the _test_pci() method, which incorrectly
enforces a restriction allowing only port-based requests, causing the
migration to fail unnecessarily.
Expected Behavior:
Live migration should succeed for flavor-based requests with NUMA
constraints, as these are now supported.
Actual Behavior:
Live migration fails due to the _test_pci() method, which wrongly
rejects flavor-based requests under the assumption that only port-
based requests are valid.
Steps to Reproduce:
Create an instance with a flavor-based request that includes NUMA constraints (e.g., CPU affinity).
Initiate a live migration.
Observe that the migration fails at the _test_pci() method due to an unnecessary restriction.
Root Cause:
The _test_pci() check is redundant as a similar verification is already performed earlier in the migration process.
The check incorrectly assumes that only port-based requests should pass, while flavor-based requests should also be allowed.
Proposed Fix:
Remove the _test_pci() method, as it is no longer necessary.
Ensure that functional tests cover mixed-mode scenarios (port-based + flavor-based requests) to prevent regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2103636/+subscriptions
Follow ups