Rebase on upstream 4.3.0.
Verified with ovirt-ansible-vm-infra-1.1.12-1.el7ev.noarch ovirt-ansible-roles-1.1.6-1.el7ev.noarch ovirt-ansible-cluster-upgrade-1.1.11-1.el7ev.noarch ovirt-ansible-infra-1.1.11-1.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.8-1.el7ev.noarch ovirt-ansible-image-template-1.1.9-1.el7ev.noarch ovirt-ansible-v2v-conversion-host-1.9.1-2.el7ev.noarch ovirt-ansible-engine-setup-1.1.7-1.el7ev.noarch ovirt-ansible-disaster-recovery-1.1.4-1.el7ev.noarch ovirt-ansible-manageiq-1.1.13-1.el7ev.noarch ovirt-ansible-repositories-1.1.4-2.el7ev.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7ev.noarch The builds are attached to the erratum and installation tests passed.
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-2019:1064