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

Bug 1613845

Summary:	[OVN][TUNNEL] Non-existent ovirt network name causes tunnel network revert to ovirtmgmt
Product:	[oVirt] ovirt-engine	Reporter:	msheena
Component:	Setup.Engine	Assignee:	Miguel Duarte Barroso <mduarted>
Status:	CLOSED CURRENTRELEASE	QA Contact:	msheena
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.2.6.1	CC:	bugs, danken, dholler, mburman, msheena
Target Milestone:	ovirt-4.3.0	Flags:	rule-engine: ovirt-4.3+
Target Release:	4.3.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_alpha	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:48:07 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:

Description msheena 2018-08-08 12:01:25 UTC

Description of problem:
When the ovn controller tunnel network is set to a network that is not the ovirtmgmt, running the Ansible playbook 
(/usr/share/ovirt-engine/playbooks/ovirt-provider-ovn-driver.yml) to change the tunnel network with the 'ovirt_network' variable set to a network name that does not exist, results in no error by the playbook, and setting the tunnel network as ovirtmgmt.

Relevant links-
https://gerrit.ovirt.org/#/c/92783/
https://bugzilla.redhat.com/show_bug.cgi?id=1565541

Version-Release number of selected component (if applicable):
ovirt-provider-ovn-1.2.14-1.el7ev.noarch
ovirt-provider-ovn-driver-1.2.14-1.el7ev.noarch
4.2.6.1_SNAPSHOT-89.g295078e.0.scratch.master.el7ev

How reproducible:
100%

Steps to Reproduce:
1. Create a vm network and attach it to all hosts in a cluster.
2. Run the playbook with ovirt_network variable set to the networks name. 
3. Verify the tunnling network indeed changed on hosts using the command:
   ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip
   this command outputs the tunneling network ip.
4. Run the playbook again with ovirt_network variable set to a non-existent 
   network name.

Actual results:
Playbook passes and tunneling network changes on hosts to ovirtmgmt.

Expected results:
Playbook fails and tunneling network on hosts stays the same.

Comment 1 Miguel Duarte Barroso 2018-10-04 10:18:26 UTC

I'm not being able to reproduce the bug; can you please post me the exact command you used on step #4 ?

Comment 2 msheena 2018-10-04 11:04:02 UTC

ansible-playbook -i /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory --extra-vars "cluster_name=<CLUSTER_NAME> ovn_central=<ENGINE_IP> ovirt_network=<NAME_OF_NETWORK_IN_WEB_UI>" /usr/share/ovirt-engine/playbooks/ovirt-provider-ovn-driver.yml

Comment 3 msheena 2018-11-20 14:25:56 UTC

Verified on:

4.3.0-0.0.master.20181119094015.gitc05e510.el7
ovirt-provider-ovn-1.2.17-1.el7.noarch
ovirt-provider-ovn-driver-1.2.17-1.el7.noarch

Comment 4 Sandro Bonazzola 2019-02-13 07:48:07 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.