DVR-Nexthop static routes are not getting configured in FIP Namespace when disassociating and reassociating a FloatingIP in Ocata

Bug #1824566 reported by Swaminathan Vasudevan on 2019-04-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Medium
Unassigned

Bug Description

Nexthop static routes for external network are not getting configured in the FIP Namespace table, after disassociating and re-associating a FloatingIP.
This is seen in Ocata and Newton. Not seen in Pike and later branches.

Steps to reproduce this problem.
1. Deploy the devstack cloud with DVR routers
2. Create a VM
3. Assign a FloatingIP to the VM.
4. Now configure a Nexthop static route for the external Network.
5. Make sure the Nexthop routes are seen in the SNAT Namespace and in the FIP Namespace under router specific lookup table-id.
6. Now Disassociate the floatingIP.
7. Make sure that the Nexthop routes are cleared from the FIP Namespace if this the only FloatingIP, under the router specific lookup table-id.
8. Now re-associate the FloatingIP.
9. Now you will see the 'Nexthop static routes' will be missing in the FIP Namespaces router specific lookup table-id.

Changed in neutron:
importance: Undecided → Medium
status: New → Confirmed
tags: added: l3-dvr-backlog
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers