Incorrect migration of instances with NUMA/CPU pinning
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Confirmed
|
Medium
|
Sergey Nikitin | |||
7.0.x |
Won't Fix
|
Medium
|
Sergey Nikitin | |||
9.x |
Won't Fix
|
Medium
|
Sergey Nikitin |
Bug Description
Upstream bug: https:/
Description:
I configured a flavor with two vcpus and extra specs "hw:cpu_
I booted up a number of instances such that there was one instance affined to host cpus 12 and 13 on compute-0, and another instance affined to cpus 12 and 13 on compute-2. (As reported by "virsh vcpupin" and "virsh dumpxml".)
I then triggered a live migration of one instance from compute-0 to compute-2. This resulted in both instances being affined to host cpus 12 and 13 on compute-2.
The "hw:cpu_
Changed in mos: | |
milestone: | 9.1 → 9.2 |
tags: | added: on-verification |
tags: | removed: on-verification |
Changed in mos: | |
status: | Fix Committed → Fix Released |
sla2 for 7.0-updates