Red Hat Bugzilla – Bug 1260381
Incorrect behavior of power saving weight module
Last modified: 2016-08-12 10:29:58 EDT
Description of problem:
Power saving weight module not work in proper way for hosts with zero vms.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have two hosts with the same CPU arch(host_1, host_2)
2. Run vm with 1Gb on host_1
3. Change scheduler policy to power_saving with default parameters
4. Start additional vm
Vm start on host_2
Vm start on host_1
Problem that when host have zero vms, engine give to host score MaxSchedulerWeight - 1(999), but hosts with vms can have score bigger than(999) because expression:
"score -= vds.getMaxSchedulingMemory() / 100;" under calcEvenDistributionScore method in EvenDistributionWeightPolicyUnit class, we can have have negative score, and then under score method in PowerSavingWeightPolicyUnit class we run "score -= calcEvenDistributionScore(vds, vm, vdsGroup != null ? vdsGroup.getCountThreadsAsCores() : false);"
we can have have score bigger than MaxSchedulerWeight score.
Possibly a bug. Martin will take a look.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving back to POST since this bug has been targeted to 4.0.1 but referenced patches are not included in 4.0.1 branch.
Please check this bug status and eventually re-target to 4.0.2.
Verified on rhevm-4.0.2-0.1.rc.el7ev.noarch