Bug 1509235

Summary:	[RFE] Define default network provider on cluster level in ansible module ovirt_cluster
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Dominik Holler <dholler>
Component:	ovirt-ansible-roles	Assignee:	Dominik Holler <dholler>
Status:	CLOSED ERRATA	QA Contact:	msheena
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	bugs, danken, dholler, fsilva, mburman, mperina, myakove, omachace
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature, ZStream
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0-0.5.alpha1.el7	Doc Type:	No Doc Update
Doc Text:	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 and will be documented in ansible, too.	Story Points:	---
Clone Of:
Clones:	1591646 (view as bug list)		Environment:
Last Closed:	2019-05-08 12:34:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1495261
Bug Blocks:	1591646

Description Dominik Holler 2017-11-03 11:51:38 UTC

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.

Comment 1 Martin Perina 2017-11-14 08:30:14 UTC

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

Comment 5 Yaniv Kaul 2018-05-13 07:23:58 UTC

The bug is missing severity and is wrongfully targeted to 4.2.3, which was released already. Please fix.

Comment 6 Dominik Holler 2018-05-14 06:01:48 UTC

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.

Comment 7 Sandro Bonazzola 2018-05-25 08:07:01 UTC

(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

Comment 8 Michael Burman 2018-06-13 13:02:02 UTC

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

Comment 9 Sandro Bonazzola 2018-06-15 08:14:43 UTC

Any ETA on ovirt-ansible-infra-1.1.6 release?

Comment 11 msheena 2019-02-13 17:06:11 UTC

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

Comment 13 errata-xmlrpc 2019-05-08 12:34:23 UTC

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