Bug 1505776

Summary:	[ovs]Can't delete tunnel system interface when delete ovs bridge directly
Product:	Red Hat Enterprise Linux 7	Reporter:	Junhan <juyan>
Component:	openvswitch	Assignee:	Timothy Redaelli <tredaelli>
Status:	CLOSED ERRATA	QA Contact:	ovs-qe
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.5	CC:	aloughla, atragler, ctrautma, egarver, fleitner, ovs-team, pvauter, sukulkar, tredaelli
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openvswitch-2.9.0-1.el7fdp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-19 10:22:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1475436

Description Junhan 2017-10-24 09:33:16 UTC

Description of problem:
When there is only one bridge,create tunnel in the bridge, then delete the bridge directly. the system tunnel interface still in.

Cause of only one bridge, backer->refcount values 1, when delete bridge "close_dpif_backer" will delete the backer, so type_run will return directly, doesn't delete the interface.

How reproducible:
always

Steps to Reproduce:
1.ovs-vsctl add-br ovsbr0
2.ovs-vsctl add-port ovsbr0 vxlan0 -- set interface vxlan0 type=vxlan option:remote_ip=11.11.11.0
3.ovs-vsctl del-br ovsbr0
4.ifconfig
Actual results:
can't delete vxlan_sys_4789

Expected results:
vxlan_sys_4789 is deleted.

Additional info:

Comment 6 Junhan 2017-10-30 02:03:18 UTC

This appears after ovs 2.8.0, when create ovs tunnel with rtnetlink.

Comment 11 Junhan 2018-02-23 07:39:37 UTC

Verified this bug in ovs 2.9.0-1.el7fdp, the vxlan_sys_4789 disappeared when deleted the ovs bridge directly. The bug has been fixed.

Comment 15 errata-xmlrpc 2018-03-19 10:22:13 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:0550