Description of problem:
Have two hosts when on first cpu loading 50% and on second 0, start new vm, vm run on host with cpu loading 0.
Version-Release number of selected component (if applicable):
is31
How reproducible:
Always
Steps to Reproduce:
1. Add two hosts, create new vm, run vm, check on what host vm started(for example host_1), poweroff vm.
2. Change cluster policy to power saving(with default parameters), load host_2 cpu to 50%
3. Run vm
Actual results:
Vm run on host_1
Expected results:
Vm run on host_2(because we have power_saving weight module)
Additional info:
Hosts have the same cpu's(same number of cpu's and cores per cpu's)
It's no logs, because no any useful information about internal scheduling process
After some discussion with Martin, revealed that weight module looks on cpu usage of host, just when it have at least one vm, so you can fast start many vms on host with cpu usage 0%, and after this because balancing policy, vm's starts to migrate on host with cpu usage 50%, one vm each balance round. Now question if it desirable behavior, if it's ok I just close this bug, if not I can close this bug and open some RFE bug.
Martin your decision?
Probably close or repurpose this bug and file the RFE. This issue only happens when you start your first Vm in the cluster so it can be considered a corner case.
Technically we do not support loading a host by something else than VMs. The logic will work properly after the first VM is started.
If you want to change this behaviour, file an RFE and propose a new behaviour.