Bug 1258751 - Balancing not take in account vms that have specific host to run
Summary: Balancing not take in account vms that have specific host to run
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.6.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ovirt-3.6.3
: 3.6.3
Assignee: Martin Sivák
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-01 08:03 UTC by Artyom
Modified: 2016-02-18 11:15 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:15:43 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
msivak: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 45559 0 master MERGED core: allow to balance migrate vm that run on specific host 2016-01-26 07:31:34 UTC
oVirt gerrit 52739 0 ovirt-engine-3.6 MERGED core: allow to balance migrate vm that run on specific host 2016-01-27 09:05:18 UTC

Description Artyom 2015-09-01 08:03:22 UTC 
Description of problem:
Balancing not take in account vms that have specific host to run

Version-Release number of selected component (if applicable):
rhevm-3.6.0-0.12.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Have two hosts without CPU loading(host_1, host_2)
2. Run once vm_1 with specific host_1 and Run once vm_2 with specific host_2(each vm have one GB of memory)
3. Load one host CPU to 50%(host_1)
4. Change cluster policy to power saving with parameters:
   Low Utilization: 20
   High Utilization: 80
   CpuOverCommitmentDuration: 1
5. Wait 5 minutes


Actual results:
No migration happen from host_2 to host_1

Expected results:
Vm from host_2 must be migrated by balancing to host_1

Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2016-01-26 07:38:58 UTC 
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.
Comment 2 Sandro Bonazzola 2016-01-27 13:46:25 UTC 
Martin, this bug is on modified and referenced in ovirt engine 3.6.3 git logs but targeted 3.6.5. Can you check?
Comment 3 Martin Sivák 2016-01-27 14:23:42 UTC 
Well I guess we should retarget it as it was already merged :)
Comment 4 Artyom 2016-02-01 13:18:04 UTC 
Verified on rhevm-backend-3.6.3-0.1.el6.noarch
Note You need to log in before you can comment on or make changes to this bug.