Description of problem: variable ksm and fence_enabled should have priority before their childs variables. clusters: ... fence_enabled: false <-- disable fence at all fence_skip_if_connectivity_broken: true fence_skip_if_sd_active: true will enable fence but it should be disabled the same situation about ksm cluster: ... ksm: false ksm_numa: true will enable ksm but it should be disabled Version-Release number of selected component (if applicable): ovirt-ansible-roles-1.0.3-1.el7ev.noarch ansible-2.3.2.0-2.el7.noarch
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