Bug 1031353

Summary: CpuOverCommitDuration not working correctly in cluster policies
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-engineAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, dfediuck, iheim, lpeer, mavital, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: is28 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 1049022    
Attachments:
Description Flags
engine and vdsm log none

Description Artyom 2013-11-17 06:25:08 UTC 
Description of problem:
CpuOverCommitDuration not working correct in cluster policies, also for Power_Saving and also for Even_Distribution policies, it's mean that if I have host with vm, that CPU of host out of define thresholds and I also have host that CPU of host in given bounds, vm start migration without waiting given in CpuOverCommitDuration field time.

Version-Release number of selected component (if applicable):
is23

How reproducible:
Always

Steps to Reproduce:
1. Add two hosts to engine, add vm and run on one of host, change cluster policy
or to Power saving or to Even Distribution, I will describe reproduce process for Even Distribution, by default CpuOverCommitDuration is 2 min and HighUtilization on 80
2. Load host CPU with running vm to 85%(you also can try some script, to run infinitive loop) 

Actual results:
Engine not waiting two minutes, but begin migration to host without loading CPU much earlier.

Expected results:
engine waiting given CpuOverCommitDuration time and just after this start migration if it still actual.

Additional info:
whole process loading CPU and waiting until vm will migrate on other host, takes less than minute
Comment 1 Artyom 2013-11-17 06:26:13 UTC 
Created attachment 825069 [details]
engine and vdsm log
Comment 3 Artyom 2013-12-19 16:35:41 UTC 
Verified on is28, vm migrate after given time.
Comment 4 Itamar Heim 2014-01-21 22:26:30 UTC 
Closing - RHEV 3.3 Released
Comment 5 Itamar Heim 2014-01-21 22:29:55 UTC 
Closing - RHEV 3.3 Released