yahoo-eng-team team mailing list archive

[Kevin Stevens <kevin@xxxxxxxxx>]

Public bug reported:

Running on Ubuntu 14.04 with Linuxbridge agent and L2pop with vxlan
networks.

In situations where "remove_fdb_entries" messages are lost/never consumed, future "add_fdb_bridge_entry" attempts will fail with the following example error message:
2015-03-16 21:10:08.520 30207 ERROR neutron.agent.linux.utils [req-390ab63a-9d3c-4d0e-b75b-200e9f5b97c6 None]
Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'bridge', 'fdb', 'add', 'fa:16:3e:a5:15:35', 'dev', 'vxlan-15', 'dst', '172.30.100.60']
Exit code: 2
Stdout: ''
Stderr: 'RTNETLINK answers: File exists\n'

In our case, instances were unable to communicate with their Neutron
router because vxlan traffic was being forwarded to the wrong vxlan
endpoint. This was corrected by either migrating the router to a new
agent or by executing a "bridge fdb del" for the fdb entry corresponding
with the Neutron router mac address. Once deleted, the LB agent added
the appropriate fdb entry at the next polling event.

If anything is unclear, please let me know.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l2-pop lb linuxbridge vxlan

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

Title:
  Add FDB bridge entry fails if old entry not removed

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Running on Ubuntu 14.04 with Linuxbridge agent and L2pop with vxlan
  networks.

  In situations where "remove_fdb_entries" messages are lost/never consumed, future "add_fdb_bridge_entry" attempts will fail with the following example error message:
  2015-03-16 21:10:08.520 30207 ERROR neutron.agent.linux.utils [req-390ab63a-9d3c-4d0e-b75b-200e9f5b97c6 None]
  Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'bridge', 'fdb', 'add', 'fa:16:3e:a5:15:35', 'dev', 'vxlan-15', 'dst', '172.30.100.60']
  Exit code: 2
  Stdout: ''
  Stderr: 'RTNETLINK answers: File exists\n'

  In our case, instances were unable to communicate with their Neutron
  router because vxlan traffic was being forwarded to the wrong vxlan
  endpoint. This was corrected by either migrating the router to a new
  agent or by executing a "bridge fdb del" for the fdb entry
  corresponding with the Neutron router mac address. Once deleted, the
  LB agent added the appropriate fdb entry at the next polling event.

  If anything is unclear, please let me know.

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