Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1591646

Summary:	[downstream clone - 4.2.4] [RFE] Define default network provider on cluster level in ansible module ovirt_cluster
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	RHV bug bot <rhv-bugzilla-bot>
Component:	ovirt-ansible-roles	Assignee:	Dominik Holler <dholler>
Status:	CLOSED ERRATA	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	bugs, danken, dholler, mburman, mperina, myakove, omachace, trichard, ylavi
Target Milestone:	ovirt-4.2.5	Keywords:	FutureFeature, ZStream
Target Release:	---	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-infra-1.1.7	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:	1509235	Environment:
Last Closed:	2018-07-31 17:51:06 UTC	Type:	---
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:	1509235
Bug Blocks:

Description RHV bug bot 2018-06-15 08:17:28 UTC

+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1509235 +++
======================================================================

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.

(Originally by Dominik Holler)

Comment 1 RHV bug bot 2018-06-15 08:17:34 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

(Originally by Martin Perina)

Comment 5 RHV bug bot 2018-06-15 08:17:47 UTC

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

(Originally by Yaniv Kaul)

Comment 6 RHV bug bot 2018-06-15 08:17:50 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.

(Originally by Dominik Holler)

Comment 7 RHV bug bot 2018-06-15 08:17:54 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

(Originally by Sandro Bonazzola)

Comment 8 RHV bug bot 2018-06-15 08:17:59 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

(Originally by Michael Burman)

Comment 9 RHV bug bot 2018-06-15 08:18:03 UTC

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

(Originally by Sandro Bonazzola)

Comment 13 Michael Burman 2018-07-24 13:09:52 UTC

Verified with ovirt-ansible-infra-1.1.7-1.el7ev.noarch

Comment 15 errata-xmlrpc 2018-07-31 17:51:06 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/RHBA-2018:2326