Bug 1540973
Summary: | hosts rule in affinity group is always enabled in rest response API (even if disabled in UI ) | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> |
Component: | BLL.Virt | Assignee: | Andrej Krejcir <akrejcir> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.1 | CC: | akrejcir, bugs |
Target Milestone: | ovirt-4.2.3 | Flags: | rule-engine:
ovirt-4.2+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature:
The host to VM affinity can now be explicitly disabled. Previously it was always enabled, but it had no effect if no hosts were assigned to the affinity group.
Reason:
Having the affinity always enabled could be confusing when using the REST API.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-10 06:33:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1493149 |
Description
Polina
2018-02-01 12:34:36 UTC
Verified on rhv-release-4.2.3-2-001.noarch. When both rules are Disabled (VM Affinity Rule & Host Affinity Rule) got the correct response. GET https://{{host}}/ovirt-engine/api/clusters/{{clusted_ID}}/affinitygroups <hosts_rule> <enabled>false</enabled> <enforcing>false</enforcing> <positive>false</positive> </hosts_rule> <vms_rule> <enabled>false</enabled> <enforcing>false</enforcing> <positive>false</positive> </vms_rule> This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |