← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1625333] Re: Booting VM with a Floating IP and pinging it via that takes a long time with errors in L3-Agent logs when using DVR

 

Terry, do you have a link to the patch? Anyway, closing the bug as
invalid because it does not affect neutron per se.

** Changed in: neutron
       Status: New => Invalid

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

Title:
  Booting VM with a Floating IP and pinging it via that takes a long
  time with errors in L3-Agent logs when using DVR

Status in neutron:
  Invalid

Bug description:
  A Rally test to launch a VM, attach a floating IP and ping the VM via
  the floating IP 40 times in case of legacy routers vs DVR routers was
  done for comparison. Time taken to create network,subnet, launch VM,
  attach floating IP etc. are similar in legacy and DVR cases but for
  the VM to be pingable via the floating ip(after it has been booted
  with floating ip) it takes a lot more time in some iterations with
  DVR. The VM is ping ready(after booting and being given a floating ip)
  in less than a second not counting time to boot or attach floating ip
  in case of Legacy. However in case of DVR sometimes we see the VM
  being ping ready in less than 1 second  whereas in some cases it takes
  around 250 seconds. Digging into the L3-agent logs on the computes we
  see this for the instances that were taking the most time to be
  pingable via the floating ip

  https://paste.fedoraproject.org/431117/74312098/

  Specifically we keep seeing errors like this:

  2016-09-19 18:58:52.675 23696 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'fip-790354c7-f286-4fd1-a4a1-ec9749c61fbf', 'arping', '-A', '-I', 'fg-6b5906d0-d9', '-c', '3', '-w', '4.5', '10.16.30.99'] execute_rootwrap_daemon /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:99
  2016-09-19 18:58:52.696 23696 ERROR neutron.agent.linux.utils [-] Exit code: 2; Stdin: ; Stdout: ; Stderr: bind: Cannot assign requested address

  2016-09-19 18:58:52.697 23696 ERROR neutron.agent.linux.ip_lib [-]
  Failed sending gratuitous ARP to 10.16.30.99 on fg-6b5906d0-d9 in
  namespace fip-790354c7-f286-4fd1-a4a1-ec9749c61fbf

  
  However, it is worth noting that bumping up the ping timeout to about 300 seconds, all VMS are pingable but it takes 100-200x the time it was taking in legacy case.

  This is the rally plugin used(create network, subnet, boot server with fip and ping):
  https://github.com/openstack/browbeat/blob/master/rally/rally-plugins/netcreate-boot-ping/netcreate_nova-boot-fip-ping.py

  The Rally results for legacy:
  https://paste.fedoraproject.org/431120/43123471/

  The Rally results for DVR:
  https://paste.fedoraproject.org/431119/47431226/

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


References