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

Bug 1422092

Summary: Avoid creating auto-tunnels for VLAN tenant networks
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: opendaylightAssignee: Sridhar Gaddam <sgaddam>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: jschluet, mkolesni, nyechiel, sgaddam
Target Milestone: asyncKeywords: ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: opendaylight-5.2.0-6.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-03-23 16:14:56 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: 1377304    

Description Itzik Brown 2017-02-14 12:59:52 UTC
Description of problem:
Currently auto-tunnel code of Netvirt is creating a Transport zone with vteps even for tenant VLAN networks. This patch updates the code to create the TZ only if the network type is VxLAN.

Version-Release number of selected component (if applicable):
opendaylight-5.2.0-2.el7ost.noarch

How reproducible:


Steps to Reproduce:
1. Create a network with type VLAN.
2. Launch an instance with an interface connected to this network.
3. Run ovs-vsctl show on the overcloud nodes and verify the tunnels are created.

Actual results:


Expected results:


Additional info:

Comment 1 Sridhar Gaddam 2017-02-14 17:08:10 UTC
Downstream patch: https://code.engineering.redhat.com/gerrit/#/c/97729/

Comment 9 Itzik Brown 2017-03-06 10:08:18 UTC
Verified with opendaylight-5.2.0-6.el7ost

Comment 11 errata-xmlrpc 2017-03-23 16:14:56 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://rhn.redhat.com/errata/RHBA-2017-0840.html