Bug 1651406
| Summary: | [RFE] Allow Maintenance of Host with Enforcing VM Affinity Rules (hard affinity) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ameya Charekar <achareka> | |
| Component: | ovirt-engine | Assignee: | Andrej Krejcir <akrejcir> | |
| Status: | CLOSED ERRATA | QA Contact: | Polina <pagranat> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.2.7 | CC: | achareka, akrejcir, fgarciad, mavital, mgoldboi, michal.skrivanek, mkalinin, myllynen, rbdiri, rdlugyhe, sbonazzo | |
| Target Milestone: | ovirt-4.4.0 | Keywords: | FutureFeature, ZStream | |
| Target Release: | --- | Flags: | mavital:
testing_plan_complete+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
The current release enables you to migrate a group of virtual machines (VMs) that are in positive enforcing affinity with each other.
* You can use the new checkbox in the Migrate VM dialog to migrate this type of affinity group.
* You can use the following REST API to migrate this type of affinity group: http://ovirt.github.io/ovirt-engine-api-model/4.4/#services/vm/methods/migrate/parameters/migrate_vms_in_affinity_closure.
* Putting a host into maintenance also migrates this type of affinity group.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1670073 1712353 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-04 13:16:18 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1670073, 1712353, 1717007 | |||
|
Description
Ameya Charekar
2018-11-20 00:40:49 UTC
This is extremely unlikely to make a 4.2 stream. 4.3 may be possible, but has soft affinity been looked at? Soft affinity (both host to VM and VM to VM) may provide an immediate resolution. This sounds extremely similar to the requirements which produced https://bugzilla.redhat.com/show_bug.cgi?id=1392393 Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both This applies to both affinity and anti-affinity. anti-affinity is going to work better, but still there will be times when the rules won't be enforced. Maintenance will have priority and if there is not enough hosts the system won't be able to distribute (or keep together) VMs properly. This should fix automatically once the host is brought back as the host becomes operational and empty/available for scheduling, though we will not attempt to restore the VM distribution exactly as it was. I propose to turn this behavior on by default in 4.3, and have an engine-config toggle to switch this off if anyone finds this new behavior problematic merged to 4.3 more patches are coming to 4.3 Not blocking ovirt-4.3.0 on this. Moving to 4.3.1. negative affinity works (fixed also in 4.2.8-1) positive affinity needs a bit more work Verified on ovirt-engine-4.3.3.6-0.0.master.20190416081415.git5975555.el7.noarch In the following cases the host maintenance is allowed: 1. Hard VM Positive and no Host Polarity 2. Soft VM Positive and no Host Polarity 3. Hard VM Positive and Soft Positive host 3. Soft VM Positive and Soft Positive host The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3247 |