Bug 1112332 – [RFE] Anti-Affinity policy does not trigger against currently running VMs

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1112332 - [RFE] Anti-Affinity policy does not trigger against currently running VMs

Summary:	[RFE] Anti-Affinity policy does not trigger against currently running VMs

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.4.0
Hardware:	x86_64 All

Priority	medium Severity medium
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Assigned To:	Tomer Saban
QA Contact:	Artyom
Docs Contact:

URL:	http://www.ovirt.org/Affinity_Group_E...
Whiteboard:
Keywords:	FutureFeature, Triaged

Duplicates:	1084518 (view as bug list)
Depends On:	1112369 1251742
Blocks:	1282800
	Show dependency tree / graph

Reported:	2014-06-23 11:54 EDT by Jake Hunsaker
Modified:	2016-04-25 07:49 EDT (History)
CC List:	19 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	The Affinity Rules Enforcement Manager has been added to check for broken affinity and anti-affinity policies and migrate virtual machines if necessary.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-03-09 15:47:55 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	sherold: Triaged+ ylavi: testing_beta_priority+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	2141771	None	None	None	2016-01-27 04:23 EST
oVirt gerrit	40990	master	MERGED	core: Start a service to solve affinity role breakage	Never
oVirt gerrit	41092	master	MERGED	core: Added affinity rules enforcement manager	Never
Red Hat Product Errata	RHEA-2016:0376	normal	SHIPPED_LIVE	Red Hat Enterprise Virtualization Manager 3.6.0	2016-03-09 20:20:52 EST

Groups: None (edit)

Description Jake Hunsaker 2014-06-23 11:54:22 EDT

Description of problem:

If an anti-affinity policy is applied to VMs that are currently running on the same hypervisor, the engine will not automatically migrate one of them off once the policy is applied. 


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

rhevm-3.4.0-0.21
vdsm-4.14.7-3.el6ev 

How reproducible:
Always

Steps to Reproduce:
1. Have two (or more) VMs running on the same hypervisor
2. Create a new anti-affinity policy and apply it to these VMs
3.

Actual results:
VMs remain running on the same hypervisor

Expected results:
Engine should detect that a new policy has been applied and migrate one of the VMs off.

Additional info:
Hard/Soft policy makes no difference on this.

Comment 6 Max Kovgan 2015-06-28 10:13:41 EDT

ovirt-3.6.0-3 release

Comment 7 Doron Fediuck 2015-08-26 10:15:05 EDT

*** Bug 1084518 has been marked as a duplicate of this bug. ***

Comment 8 Artyom 2015-09-22 02:27:58 EDT

Verified on rhevm-3.6.0-0.16.master.el6.noarch
Polarion test run https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/testrun?id=3%5F6%5FSLA%5FBalance%5FCluster%5FVMS%5Faffinity%5F21092015

Comment 10 errata-xmlrpc 2016-03-09 15:47:55 EST

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/RHEA-2016-0376.html

Note You need to log in before you can comment on or make changes to this bug.