Bug 1126839
Summary: | "There is no over-utilized host in cluster " repeated every minute | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Paul Dwyer <pdwyer> |
Component: | ovirt-engine | Assignee: | Doron Fediuck <dfediuck> |
Status: | CLOSED ERRATA | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | dfediuck, ecohen, gklein, iheim, lpeer, mavital, rbalakri, Rhev-m-bugs, yeylon |
Target Milestone: | --- | ||
Target Release: | 3.5.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | sla | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-11 18:07:07 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
Paul Dwyer
2014-08-05 12:22:47 UTC
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 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 |