Bug 1505835 - SNAT Managment Ip Address is not updated for a router
Summary: SNAT Managment Ip Address is not updated for a router
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opendaylight
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-24 11:16 UTC by Itzik Brown
Modified: 2018-10-24 12:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-11-21 12:39:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Itzik Brown 2017-10-24 11:16:20 UTC
Description of problem:

In HA Setup - after creating a router,setting it's gateway and adding an internal interface.

Then running on the controller the following command 

[root@controller-0 heat-admin]# sudo docker exec --user root -it opendaylight_api /opt/opendaylight/bin/client -u karaf display-napt-switches
Router Id                 Datapath Node Id      Managment Ip Address
    -------------------------------------------------------------------------------------------
     cf09640c-6efb-46fe-9c10-da87e1bb9ec3  0         null                
     e9872b64-a134-451f-86e4-c50388c2fa63  0         null


There is no Managment Ip Address for the router.

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

How reproducible:


Steps to Reproduce:
1. Setup OpenStack with OpenDaylight on HA setup
2. Create an external network,a router and an internal network
3. Set the gateway for the router and attach the internal interface 
4. On one of the controllers run:
   $ sudo docker exec --user root -it opendaylight_api /opt/opendaylight/bin/client -u karaf display-napt-switches
5. Verify that there is no Managment Ip Address for the router

Actual results:


Expected results:


Additional info:


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