yahoo-eng-team team mailing list archive

[OpenStack Infra <1571676@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/308068
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c6de850021d099d6bad026b2192ea40b9c849f87
Submitter: Jenkins
Branch:    master

commit c6de850021d099d6bad026b2192ea40b9c849f87
Author: Swaminathan Vasudevan <swaminathan.vasudevan@xxxxxxx>
Date:   Tue Apr 19 15:45:04 2016 -0700

    DVR: Add static routes to FIP namespace
    
    The static routes are currently only added to the router
    namespace and snat namespace, but not added to the fip
    namespace.
    
    This patch adds the static routes configured for the router
    to the FIP namespace, to its own table. So this will allow
    the FIP namespace to be configured with different nexthop
    routes for different routers.
    
    Change-Id: Ida165d1ecf5c07af31dac11d9daed33ccaaf5605
    Closes-Bug: #1571676


** Changed in: neutron
       Status: In Progress => 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/1571676

Title:
  After binding a floating IP to VM, the static route can't work in DVR.

Status in neutron:
  Fix Released

Bug description:
  In DVR topology, in order to arrived target host, a static route entry
  has been added to vrouter.

  1>. Before associate a floating IP to VM, the traffic from VM to
  target host via the router(SNAT-NS) is OK.

     Gateway ------- vrouter(SNAT-NS) ------- VM
          |
          |
     Target HOST

  2>. Then I associate a floating IP to VM, the VM can't ping to target
  host now.

     Gateway ------- vrouter(FIP-NS) ------- VM
          |
          |
     Target HOST

    I have checked the router in SNAT-NS and FIP-NS, found the static
  router entry is added to SNAT-NS, but it missed in FIP-NS.

  
  Append detail info:

  Internet
      |
      |
      |
  GW<----->Server1(nic1:172.16.0.10,nic2:172.18.0.10)<---->target host(172.18.0.56)
      |
      |(external-net)
      |
  FIP(192.168.0.1/172.16.0.5)
      |
      |(internal-net)
      |
  VM(192.168.0.6)

  1> The IP of target host is 172.18.0.56/24
  2> The IP of external GW is 172.16.0.1, but the IP of internal GW is 192.168.0.1, they are different.
  3> The exact router in snat namespace is the same as it in router namespace(172.18.0.0/24 via 172.16.0.10 dev XXX ), can't find this route entry in FIP namespace.

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