yahoo-eng-team team mailing list archive

[James Denton <james.denton@xxxxxxxxxxxxx>]

Public bug reported:

Version: 2015.2 (Liberty)
Plugin: ML2 w/ LinuxBridge

While testing various NICs, I found that changing the physical interface
mapping in the ML2 configuration file and restarting the agent resulted
in the old physical interface remaining in the bridge. This can be
observed with the following steps:

Original configuration:

[linux_bridge]
physical_interface_mappings = physnet1:eth2

racker@compute01:~$ brctl show
bridge name       bridge id          STP enabled   interfaces
brqad516357-47    8000.e41d2d5b6213  no            eth2
                                                   tap72e7d2be-24

Modify the bridge mapping:

[linux_bridge]
#physical_interface_mappings = physnet1:eth2
physical_interface_mappings = physnet1:eth1

Restart the agent:

racker@compute01:~$ sudo service neutron-plugin-linuxbridge-agent restart
neutron-plugin-linuxbridge-agent stop/waiting
neutron-plugin-linuxbridge-agent start/running, process 12803

Check the bridge:

racker@compute01:~$ brctl show
bridge name       bridge id          STP enabled   interfaces
brqad516357-47    8000.6805ca37dc39  no            eth1
                                                   eth2
                                                   tap72e7d2be-24

This behavior was observed with flat or vlan networks, and can result in
some wonky behavior. Removing the original interface from the bridge(s)
by hand or restarting the node is a workaround, but I suspect
LinuxBridge users aren't used to modifying the bridges manually as the
agent usually handles that.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Changing physical interface mapping may result in multiple physical
  interfaces in bridge

Status in neutron:
  New

Bug description:
  Version: 2015.2 (Liberty)
  Plugin: ML2 w/ LinuxBridge

  While testing various NICs, I found that changing the physical
  interface mapping in the ML2 configuration file and restarting the
  agent resulted in the old physical interface remaining in the bridge.
  This can be observed with the following steps:

  Original configuration:

  [linux_bridge]
  physical_interface_mappings = physnet1:eth2

  racker@compute01:~$ brctl show
  bridge name       bridge id          STP enabled   interfaces
  brqad516357-47    8000.e41d2d5b6213  no            eth2
                                                     tap72e7d2be-24

  Modify the bridge mapping:

  [linux_bridge]
  #physical_interface_mappings = physnet1:eth2
  physical_interface_mappings = physnet1:eth1

  Restart the agent:

  racker@compute01:~$ sudo service neutron-plugin-linuxbridge-agent restart
  neutron-plugin-linuxbridge-agent stop/waiting
  neutron-plugin-linuxbridge-agent start/running, process 12803

  Check the bridge:

  racker@compute01:~$ brctl show
  bridge name       bridge id          STP enabled   interfaces
  brqad516357-47    8000.6805ca37dc39  no            eth1
                                                     eth2
                                                     tap72e7d2be-24

  This behavior was observed with flat or vlan networks, and can result
  in some wonky behavior. Removing the original interface from the
  bridge(s) by hand or restarting the node is a workaround, but I
  suspect LinuxBridge users aren't used to modifying the bridges
  manually as the agent usually handles that.

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