Bug 1261880 - [RFE] Consider hard affinity group migration, as opposed to current state (blocking migration)
[RFE] Consider hard affinity group migration, as opposed to current state (bl...
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: RFEs (Show other bugs)
All Linux
medium Severity high (vote)
: ---
: ---
Assigned To: nobody nobody
: FutureFeature, Improvement
Depends On:
  Show dependency treegraph
Reported: 2015-09-10 07:21 EDT by Artyom
Modified: 2017-09-28 05:46 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ylavi: ovirt‑future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

  None (edit)
Description Artyom 2015-09-10 07:21:49 EDT
Description of problem:
Available to put host to maintenance, when it have at least two vms, that included in hard positive affinity group.
In 3.4 we blocked such possibility, to prevent race condition between vms migration, but now we queue of pending vms and it possible to avoid race condition.

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

How reproducible:

Steps to Reproduce:
1. Create hard positive affinity group with two vms(vm_1, vm_2)
2. Start both vms(run on the same host)
3. Put host to maintenance

Actual results:
Status: 409
Reason: Conflict
Detail: [Cannot switch Host(s) to Maintenance mode.
The following Enforcing Affinity Group(s) have running VMs and can break the affinity rule.
maintenance_hard_positive_affinity_group (golden_env_mixed_virtio_0 ,golden_env_mixed_virtio_1)
Please manually migrate the VMs, or change Affinity Group's enforcing to false.]

Expected results:
Action succeed and vms migrated to same host

Additional info:
We need take in account, that destination host will not have resources to run both vms, in such case we need to failed host maintenance with appropriate message

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