Description of problem:
When instance has pinned cpus in a given numa zone, evacuation will try to schedule the same cpus/numa zone on another compute and this will fail if the same cpus/numa zone is taken . If the cpus / numa zone are free, scheduling will pass and the VM will actually be rebuilt on the new compute. It looks like NUMAToplogyFilter tries to find the same topology on a different host.
This is when hw:cpu_policy=dedicated is being used. We feel like this is a bug.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Based on our IRC conversations, I'm closing this as NOTABUG for now. It looks like the NUMA topology filter was correct after all in thinking that not enough CPUs were available. If this turns out not to be the case, by all means reopen this bug.