Bug 1491244
Summary: | [ovirt-ansible-roles] ovirt-clusters: variable ksm and fence_enabled should have priority before their childs variables | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Kubica <pkubica> |
Component: | ovirt-ansible-roles | Assignee: | Ondra Machacek <omachace> |
Status: | CLOSED ERRATA | QA Contact: | Petr Kubica <pkubica> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.6 | CC: | mperina, pkubica, pstehlik |
Target Milestone: | ovirt-4.2.2 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-ansible-roles-1.1.1-0.el7ev | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 18:00:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Kubica
2017-09-13 11:42:45 UTC
fence_enabled: false fence_skip_if_connectivity_broken: true fence_skip_if_sd_active: true still fence_enabled is enabled in engine (should be disabled) too, with ksm: false ksm_numa: true trying to update existung cluster where: ksm: true ksm_numa: true at first run ovirt-ansible-infra-1.1.2-1.el7ev.noarch ansible-2.4.1.0-1.el7ae.noarch too, with ksm: false ksm_numa: true trying to update existing cluster where: ksm: true ksm_numa: true at first run ovirt-ansible-infra-1.1.2-1.el7ev.noarch ansible-2.4.1.0-1.el7ae.noarch Can you try with Ansible 2.4.2? Verified with: ansible-2.4.2.0-2.el7.noarch ovirt-ansible-infra-1.1.3-1.el7ev.noarch 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, 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/RHEA-2018:1534 BZ<2>Jira Resync |