Red Hat Bugzilla – Bug 1126839
"There is no over-utilized host in cluster " repeated every minute
Last modified: 2016-02-10 15:19:51 EST
Description of problem: When using Even Distribution policy the following message gets logged every minute "There is no over-utilized host in cluster" Version-Release number of selected component (if applicable): RHEVM3.4 How reproducible: Always Steps to Reproduce: 1. Utilise Even Distribution policy Actual results: The message is logged every minute. Expected results: It is fine to run the check every minute but why do we need to log the fact that there is nothing to balance. Additional info: Looking at the code [ovirt-engine.git] / backend / manager / modules / bll / src / main / java / org / ovirt / engine / core / bll / scheduling / policyunits / EvenDistributionBalancePolicyUnit.java Wouldn't it make more sense for that to be log.debugFormat? 55 // if there aren't any overutilized hosts, then there is nothing to balance... 56 if (overUtilizedHosts == null || overUtilizedHosts.size() == 0) { 57 log.infoFormat("There is no over-utilized host in cluster '{0}'", cluster.getName()); 58 return null; 59 }
this bug status was moved to MODIFIED before engine vt5 was built, hence moving to on_qa, if this was mistake and the fix isn't in, please contact rhev-integ@redhat.com
still reproducible in vt7 2014-10-23 11:52:23,312 INFO [org.ovirt.engine.core.bll.scheduling.PolicyUnitImpl] (DefaultQuartzScheduler_Worker-41) There is no over-utilized host in cluster Default 2014-10-23 11:53:23,317 INFO [org.ovirt.engine.core.bll.scheduling.PolicyUnitImpl] (DefaultQuartzScheduler_Worker-97) There is no over-utilized host in cluster Default 2014-10-23 11:54:23,326 INFO [org.ovirt.engine.core.bll.scheduling.PolicyUnitImpl] (DefaultQuartzScheduler_Worker-53) There is no over-utilized host in cluster Default 2014-10-23 11:55:23,330 INFO [org.ovirt.engine.core.bll.scheduling.PolicyUnitImpl] (DefaultQuartzScheduler_Worker-12) There is no over-utilized host in cluster Default
The patch wasn't picked to the 3.5 branch. Re-submitted.
verified in av13.4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html