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):
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
VMs remain running on the same hypervisor
Engine should detect that a new policy has been applied and migrate one of the VMs off.
Hard/Soft policy makes no difference on this.
*** Bug 1084518 has been marked as a duplicate of this bug. ***
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
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.