Bug 1251742

Summary: Affinity balancing stop work after first migration
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-engineAssignee: Roman Mohr <rmohr>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.6.0CC: dfediuck, gklein, istein, lpeer, lsurette, mgoldboi, rbalakri, rgolan, Rhev-m-bugs, srevivo, tsaban, ykaul
Target Milestone: ovirt-3.6.0-rcKeywords: Triaged
Target Release: 3.6.0Flags: mgoldboi: Triaged+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Consequence: Result: Fix:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 01:11:49 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:
Bug Depends On:    
Bug Blocks: 1112332    
Attachments:
Description Flags
engine log none

Description Artyom 2015-08-09 13:18:25 UTC
Description of problem:
No affinity balancing of vms that placed in the same hard, negative affinity group

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150804111407.git122a3a0.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add two hosts
2. Add two vms
3. Start vms on the same host
4. Add two vms to the hard, negative affinity group
5. Wait until affinity balancing will move one of vm to another host

Actual results:
Vms still placed on the same host, and I do not see any exceptions in engine log

Expected results:
One of vm must be moved to another host

Additional info:
I do not see any exceptions under engine log, but if you will need it anyway, leave me needinfo

Comment 1 Artyom 2015-08-09 15:22:08 UTC
Created attachment 1060747 [details]
engine log

After additional investigation with Roy, found that balancing happen just first time after engine restart and after first migration balancing stop work.

Comment 2 Tomer Saban 2015-08-16 10:26:40 UTC
There has been a logical issue in the method checkIfCurrentlyMigrating. So I added a patch that fixes it.

Comment 3 Artyom 2015-09-21 12:22:47 UTC
Verified on rhevm-3.6.0-0.16.master.el6.noarch

Comment 4 Roman Mohr 2016-01-19 10:28:48 UTC
Was never part of an official release and was completely reimplemented.