Bug 1667842 - Automatic Migration for Affinity Labels not working
Summary: Automatic Migration for Affinity Labels not working
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.1
: 4.3.0
Assignee: Andrej Krejcir
QA Contact: Polina
Depends On:
TreeView+ depends on / blocked
Reported: 2019-01-21 09:40 UTC by Marko Myllynen
Modified: 2019-05-08 12:39 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-
Doc Type: Enhancement
Doc Text:
Previously, the background process to migrate virtual machines considered affinity groups. This release updates the background process to migrate virtual machines to consider both affinity groups and affinity labels.
Clone Of:
Last Closed: 2019-05-08 12:39:10 UTC
oVirt Team: Virt
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1085 0 None None None 2019-05-08 12:39:21 UTC
oVirt gerrit 97463 0 master MERGED core: Consider Labels during affinity enforcement 2019-02-13 11:51:42 UTC

Description Marko Myllynen 2019-01-21 09:40:17 UTC
Description of problem:
RHV 4.2 Virtual Machine Management Guide states (chapter 6.12):

Labels function identically to a hard positive affinity group, but simplify configuration in certain use case.

However, we've noticed a small difference between these:

1. Create labels for Hosts
2. Define labels for VMs
3. Startup VMs
4. Verify VM placement being ok
5. Change labels for Hosts
6. Observe changes

With Affinity Labels we see that VMs won't migrate to other allowed Hosts automatically if removing the allowed label from the current Host, you either need to shutdown and restart them or migrate them manually. With Host/VM Affinities this is not needed, VMs migrate to the Hosts as per the updated Host/VM Affinities without any manual intervention.

According to Andrej the automatic migration for affinity labels was not implemented and he thinks it probably should be.


Comment 2 Polina 2019-02-17 16:55:42 UTC
Verified on ovirt-engine- according to the cases RHEVM-26207 - RHEVM-26211 added to the 

Comment 4 meital avital 2019-02-26 13:38:05 UTC
Moving to verified according to comment #2

Comment 6 errata-xmlrpc 2019-05-08 12:39:10 UTC
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.


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