yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1571676@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

-- 
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:
  Expired

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