yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1736650@xxxxxxxxxxxxxxxxxx>]

Bug closed due to lack of activity, please feel free to reopen if
needed.

** 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/1736650

Title:
  linuxbrige manages non linuxbridge ports

Status in neutron:
  Won't Fix

Bug description:
  In our ML2 environment we have 2 mech drivers, linuxbridge and
  midonet.

  We have linuxbridge and midnet networks bound to instances on the same
  compute nodes. All works well except the midonet ports get marked as
  DOWN. I've traced this back to the linuxbridge agent.

  It seems to mark the midonet ports as DOWN. I can see the midonet port
  IDs in the linuxbridge logs.

  Steps to reproduce:

  Config:

  [ml2]
  type_drivers=flat,midonet,uplink
  path_mtu=0
  tenant_network_types=midonet
  mechanism_drivers=linuxbridge,midonet

  
  Boot an instance with a midonet nic, you will note port is DOWN.
  Stop linuxbridge agent and repeat, port will be ACTIVE
  start linux bridge agent and existing midonet ports will change to DOWN

  
  This is running stable/ocata

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