Bug 1353059
Summary: | Slightly misleading log when using OptimalForPowerSaving Balancer. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
Component: | ovirt-engine | Assignee: | Yanir Quinn <yquinn> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Shira Maximov <mshira> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.7 | CC: | amarchuk, dfediuck, gklein, lsurette, mavital, mgoldboi, rbalakri, rgolan, Rhev-m-bugs, sbonazzo, srevivo, ykaul, yquinn |
Target Milestone: | ovirt-4.0.4 | ||
Target Release: | 4.0.4 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-10-17 13:08:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Germano Veit Michel
2016-07-06 00:24:17 UTC
Is this going to 4.0? 1. It cannot be set to 4.0.4 - this is our RC cycle, or even post RHV 4.0 GA - we don't want that. 2. Patches are still in draft. What is the status of this bug? (In reply to Yaniv Kaul from comment #1) > Is this going to 4.0? > 1. It cannot be set to 4.0.4 - this is our RC cycle, or even post RHV 4.0 GA > - we don't want that. > 2. Patches are still in draft. > > What is the status of this bug? 1.need to verify with Doron / Roy 2.The patch is pending on code review (both on master and 4.0) Also the wording "Secondary method" is not helping. verified on : Red Hat Virtualization Manager Version: 4.0.4-0.1.el7ev verification steps: 1. create new cluster policy with OptimalForPowerSaving LOAD Balancer and the following parameters: - MinFreeMemoryForUnderUtilized of X GB - MaxFreeMemoryForOverUtilized of Y GB 2. set this new cluster policy on the cluster 3. Concentrate all VMs in one host, let it go under Y of free scheduling memory 4. Let the other host have more free memory than X can see the right Warning log : 2016-09-05 14:55:40,422 WARN [org.ovirt.engine.core.bll.scheduling.policyunits.CpuAndMemoryBalancingPolicyUnit] (DefaultQuartzScheduler9) [422a7cba] All candidate hosts have been filtered, can't balance the cluster 'golden_env_mixed_1' using memory based approach |