yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

Marked as won't fix.

A bridge removed from bridge-mappings won't be handled or know by the
neutron agent.

A note was added to documentation:

https://review.openstack.org/168084

** Changed in: neutron
       Status: New => 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/1436267

Title:
  Removing bridge_mappings could lead to network broadcast storms

Status in neutron:
  Won't Fix

Bug description:
  Old patch ports and openflow rules could lead to loops

  If we remove bridges from bridge_mappings they're still connected to br-int..
  This could lead to a network loop, depending on the topology of your bridges for external networks.

  We encountered a situation where we had a loop formed over:

  eth1->br-ex->br-int->br-ex2->eth2

  Generally that traffic is tagged by br-int at entrance, but once
  the bridge_mappings are cleared, and the agent is restarted
  those flows go away, and NORMAL forwarding rules apply.

  This situation could have been alleviated across reboots if
  the br-ex & br-ex2 was set to secure fail-mode when the agent
  configures patch ports and openflow rules in both bridges.

  I will propose a patch to do that.

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