← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1456624] Re: DVR Connection to external network lost when associating a floating IP

 

In my review of the patch, I stated that I think the cure is much worse
than the problem.  I don't think anyone has chimed in to change my mind
and so I'm marking this as won't fix.  Ping me if you think it should be
fixed.

** Changed in: neutron
       Status: Confirmed => Won't Fix

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

Title:
  DVR Connection to external network lost when associating a floating IP

Status in neutron:
  Won't Fix

Bug description:
  In DVR, when a floating ip is associated with a port, the current
  connection( ssh or ping) to external network will be hung(and
  unresponsive).

  The connection may be any TCP, UDP, ICMP connections which are tracked
  in conntrack.

  Having a distributed router with interfaces for an internal network
  and external network.

  When Launching a instance and pinging an external network and then associating a floating to the instance the connection is lost i.e.
   the ping fails.
  When running the ping command again - it's successful.

  Version
  ======
  RHEL 7.1
  python-nova-2015.1.0-3.el7ost.noarch
  python-neutron-2015.1.0-1.el7ost.noarch

  How to reproduce
  ==============
  1. Create a distributed router and attach an internal and an external network to it.
      # neutron router-create --distributed True router1
      # neutron router-interface-add router1 <subnet1 id>
      # neutron router-gateway-set <external network id>

  2. Launch an instance and associate it with a floating IP.
      # nova boot --flavor m1.small --image fedora --nic net-id=<internal network id> vm1

  3. Go to the console of the instance and run ping to an external network:
       # ping 8.8.8.8

  4.  Associate a floating IP to the instance:
       # nova floating-ip-associate vm1 <floatingip-address>

  5. Verify that the ping fails.

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


References