Bug 1513464

Summary: In conntrack SNAT Vpn to dpn maps fails to update when a subnet is added/removed
Product: Red Hat OpenStack Reporter: Aswin Suryanarayanan <asuryana>
Component: opendaylightAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: urgent Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: mkolesni, nyechiel
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: opendaylight-6.2.0-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2018-06-27 13:39:31 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:

Description Aswin Suryanarayanan 2017-11-15 13:10:11 UTC
Description of problem:
In conntrack SNAT Vpn to dpn maps fails to update when a subnet is added/removed

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1)Create a external router and set as the router as g/w
2)Add subnets to the router.
3)The subnet router port needs to be added to vpn to Dpn map.

Actual results:
The router port is not added.

Expected results:
The router port should be added.

Comment 1 Aswin Suryanarayanan 2017-11-15 13:16:04 UTC
https://code.engineering.redhat.com/gerrit/#/c/122748/

Comment 8 Itzik Brown 2018-03-22 08:38:02 UTC
Verified with:
opendaylight-8.0.0-2.el7ost.noarch

1. Created an internal network and an external network
2. Launched an instance connected to the internal network
3. Created a router and add the gateway info
4. Verified the NAPT switch is not on the same node as the instance
5. Added the internal interface to the router
6. Checked connectivity from the instance to an external IP

Comment 10 errata-xmlrpc 2018-06-27 13:39:31 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-2018:2086