+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1653752 +++ ====================================================================== Description of problem: When migrating a VM, the scheduler subtracts the CPU load of the VM from the host where it is currently running. So that the host can appear as if the VM is not running there. This calculation is incorrect when the cluster does not have option 'count threads as cores' set. Version-Release number of selected component (if applicable): 4.3 and 4.2 Steps to Reproduce: 1. Unset the 'count threads as cores' option for the cluster. 2. Have 2 hosts (host1, host2) with 2 threads per CPU core. 3. Run 2 VMs (VM1, VM2) on host1. With the same number of cores as the host, but 1 thread per core. 4. Add VM1 and host1 to an affinity group, positive, enforcing. 5. Create 100% CPU load on VM2. (for example by running: python -c 'while True: pass') 6. Enable EvenDistribution balancing on the cluster. Set HighUtilization to 50. 7. Wait to see if the VM2 will be migrated to host2 by the balancing. Actual results: VM2 is not migrated. Scheduler incorrectly computes the CPU load of host1, so the host is considered the best candidate for migration and the VM does not migrate. Expected results: VM2 migrates to host2. (Originally by Andrej Krejcir)
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops
Martin, Could you please take care of acking this bug? Thanks
Tested on: ovirt-engine-4.2.8.2-0.1.el7ev.noarch Forth to https://bugzilla.redhat.com/show_bug.cgi?id=1653752#c2 Moving back to assign.
Closing -- leaving tracking in the upstream bug for 4.3