yahoo-eng-team team mailing list archive

[Swaminathan Vasudevan <souminathan@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1824566

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

Status in neutron:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1824566/+subscriptions