Hi, This is the expected behavior. The process that automatically migrates VMs so that they do not break affinity groups, only migrates one VM at a time. In this case the two VMs are in a positive enforcing group, so none of them can be migrated away from the other.
Currently, for the same reason, the 2 VMs cannot even be migrated manually. But that will be fixed as part of RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1651406 Best regards, Andrej On Wed, 13 Mar 2019 at 08:50, <[email protected]> wrote: > Hi there, > Here is my setup: > oVirt engine: 4.2.8 > > 1. Create an affinity group as below: > VM affinity rule: positive + enforcing > Host affinity rule: disabled. > VMs: 2 VMs added > Hosts: No host selected. > 2. Run the 2 VMs, they are running on the same host, say host1. > 3. Change the affinity group's host affinity: > Host affinity rule: positive + enforcing > Hosts: host2 added. > > I expect that the 2 VMs can migrate to host2, but that never happen, is > this expected? > > snippet of engine.log: > 2019-03-13 07:47:05,747Z INFO > [org.ovirt.engine.core.bll.scheduling.SchedulingManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] Candidate host > 'dub-svrfarm24' ('76b13e75-d01b-4dec-9298-1fad72b46525') was filtered out > by 'VAR__FILTERTYPE__INTERNAL' filter 'VmAffinityGroups' (correlation id: > null) > 2019-03-13 07:47:05,747Z DEBUG > [org.ovirt.engine.core.bll.scheduling.arem.AffinityRulesEnforcer] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] VM > 822b37b7-5da3-453c-b775-d4192c2fdcae is NOT a viable candidate for solving > the affinity group violation situation. > 2019-03-13 07:47:05,747Z DEBUG > [org.ovirt.engine.core.bll.scheduling.arem.AffinityRulesEnforcer] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] No vm to hosts > soft-affinity group violation detected > 2019-03-13 07:47:05,749Z DEBUG > [org.ovirt.engine.core.bll.scheduling.arem.AffinityRulesEnforcer] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] No affinity group > collision detected for cluster 8fe88b8c-966c-4c21-839d-e2437cc6b73d. > Standing by. > 2019-03-13 07:47:05,749Z DEBUG > [org.ovirt.engine.core.bll.scheduling.arem.AffinityRulesEnforcer] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] No affinity group > collision detected for cluster 3beac2ea-ed04-4f40-9ce3-5a9a67cebd8c. > Standing by. > 2019-03-13 07:47:05,750Z DEBUG > [org.ovirt.engine.core.bll.scheduling.arem.AffinityRulesEnforcer] > (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] No affinity group > collision detected for cluster da32d154-4303-11e9-9607-00163eaab080. > Standing by. > > Thank you, > -Zhen > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/2BVS3U4BBFLJ32EZN5K3TOI64M7DQHSZ/ >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/3W7KG63II7PLJIMEJLL3TPO3HCRIXL2D/
