Bug 1261880 - [RFE] Consider hard affinity group migration, as opposed to current state (blocking migration)
Summary: [RFE] Consider hard affinity group migration, as opposed to current state (bl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-10 11:21 UTC by Artyom
Modified: 2019-04-28 10:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-26 16:19:47 UTC
oVirt Team: SLA
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1265467 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1265467

Description Artyom 2015-09-10 11:21:49 UTC
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):
rhevm-3.6.0-0.13.master.el6.noarch

How reproducible:
Always

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

Comment 1 Martin Sivák 2018-06-26 16:19:47 UTC
Closing based on the same reasons as were mentioned in bug 1265467


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