Bug 1551544

Summary:	VM affinity rules no longer respected since upgrade from 4.1 to 4.2
Product:	[oVirt] ovirt-engine	Reporter:	Rik Theys <rik.theys>
Component:	General	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Polina <pagranat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.1.4	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-07 11:31:39 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 Rik Theys 2018-03-05 12:02:40 UTC

Description of problem:

I upgraded our oVirt engine (and hosts) from 4.1 to 4.2.1. After the upgrade I've noticed that the VM affinity rules I've specified are no longer respected.

When I edit the affinity group, the VM affinity rule shows 'disabled'. I can change it to 'negative' and save it. But when I click edit again it shows disabled again. 

The rules are also not respected by the scheduler as both VM's in the group are started on the same host when powered down/up again.

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


How reproducible:


Steps to Reproduce:
1. Set soft negative affinity rules for 2 VM's
2. Boot the 2 VM's
3.

Actual results:
Both VM's are running on the same host

Expected results:
VM's running on different hosts.

Additional info:

It seems the properties can no longer be changed.

Comment 1 Martin Sivák 2018-03-07 11:31:39 UTC


*** This bug has been marked as a duplicate of bug 1540955 ***