8ffaac4932
When one resizes a pinned instance, the instance claims host CPUs for
pinning purposes on the destination. However, the host CPUs on the
source are not immediately relinquished. Rather, they are held by the
migration record, to handle the event that the resize is reverted. It is
only when one confirms this resize that the old cores are finally
relinquished.
It appears there is a potential race between the resource tracker's
periodic task and the freeing of these resources, resulting in attempts
to unpin host cores that have already been unpinned. This test
highlights that bug pending a fix.
Change-Id: Ie092628ac71eb87c9dfa7220255a2953ada9e04d
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Related-Bug: #1879878
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| base.py | ||
| integrated_helpers.py | ||
| test_evacuate.py | ||
| test_numa_servers.py | ||
| test_pci_sriov_servers.py | ||
| test_report_cpu_traits.py | ||
| test_reshape.py | ||
| test_rt_servers.py | ||
| test_shared_resource_provider.py | ||
| test_vgpu.py | ||
| test_vpmem.py | ||