Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1513464 - In conntrack SNAT Vpn to dpn maps fails to update when a subnet is added/removed
In conntrack SNAT Vpn to dpn maps fails to update when a subnet is added/removed
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: opendaylight (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
high Severity urgent
: beta
: 13.0 (Queens)
Assigned To: Aswin Suryanarayanan
Itzik Brown
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-15 08:10 EST by Aswin Suryanarayanan
Modified: 2018-10-18 03:22 EDT (History)
2 users (show)

See Also:
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 09:39:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenDaylight gerrit 65124 None None None 2017-11-15 08:12 EST
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:40 EDT

  None (edit)
Description Aswin Suryanarayanan 2017-11-15 08:10:11 EST
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 08:16:04 EST
https://code.engineering.redhat.com/gerrit/#/c/122748/
Comment 8 Itzik Brown 2018-03-22 04:38:02 EDT
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 09:39:31 EDT
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

Note You need to log in before you can comment on or make changes to this bug.