yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@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/1229548

Title:
  Advanced service router becomes destination of a floating ip for a
  short period of time

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  If we initiate a connection to a floating ip right after
  creating/associating it with a VM's port, the connection goes to
  advanced service router for a short period if time, instead to the VM
  the floating ip is supposed to be associated with.

  The root cause is when creating/associating a floating ip using
  advanced service router, in addition to create a DNAT rule, we also
  need to configure the floating ip on advanced service router's vNic so
  the advanced service router can reply ARP request for that IP. We
  configure the IP on the vnic before the DNAT rule is configured,
  therefore, there is a small window, after IP is configured but before
  DNAT is configured, that the traffic to floating IP will reach
  advanced service router.

  The fix is to configure the DNAT rule before applying the IP on
  advanced service router's vNic.

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