Description of problem: All oVirt hosts, which could host a VM with an interface attached to an external, e.g. OVN, network. If the VM is not pinned to specific hosts, any host in the VM’s cluster can host the VM. For this reason, all hosts in the cluster need to provide the external network. To manage the availability of an external network over all hosts of a cluster, the cluster is extended by a default network provider, which should be supported by every host in the cluster, if the host does not explicitly overwrite. It should be possible to define the default network provider of a cluster if the cluster is created via ansible. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a cluster in ansible 2. 3. Actual results: Cluster has no default network provider Expected results: Cluster has the requested default network provider Additional info: The affected software is ansible, but creating the bug here for a homogeneous tracking.
This is not an RESTAPI change, but a change in Ansible module, so this fix will be contained in upcoming ansible-2.5.0 release
The bug is missing severity and is wrongfully targeted to 4.2.3, which was released already. Please fix.
This bug is fixed in ansible 2.5 and ovirt-ansible-infra-1.1.6 (depends on ansible 2.5). I will check the RHV version this maps.
(In reply to Dominik Holler from comment #6) > This bug is fixed in ansible 2.5 and ovirt-ansible-infra-1.1.6 (depends on > ansible 2.5). I will check the RHV version this maps. Moving to QE being ansible 2.5.3 released in ansible engine channel. https://access.redhat.com/errata/RHBA-2018:1692
Moving back to modified as ovirt-ansible-infra-1.1.6 not yet available. We currently have ovirt-ansible-infra-1.1.5-1.el7ev.noarch ansible-2.5.4-1.el7ae.noarch
Any ETA on ovirt-ansible-infra-1.1.6 release?
Verified on: (Red Hat Enterprise Virtualization Manager) 4.3.0.4-0.1.el7 ovirt-engine-sdk-python 4.2.6 ansible 2.5.2
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