← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1240874] Re: LinuxBridge plugin fails with multiple VM NICs when gateway configs differ

 

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

Title:
  LinuxBridge plugin fails with multiple VM NICs when gateway configs
  differ

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Specifically, the linux bridge plugin fails when spawning a VM with
  multiple networks, where those networks have different gateway enabled
  / disabled settings.  Homogeneous network gateway settings for
  multiple networks works fine, however.  In other words:

  -Spawning a VM with two NICs, both which have a Gateway IP configured,  results in an Active instance (good)
  -Spawning a VM with two NICs, both which have the Gateway disabled, results in an Active instance (good)
  -Spawning a VM with two NICs, one which has a Gateway IP configured, and the other that has gateway disabled results in a Failed instance (bad).

  I have attached the stack trace for the plugin error it produced.

  The error seems to indicate a failure to add the tap device to the
  bridge, because the tap device doesn't exist.  However, it does appear
  that the interface is being created - if only briefly before being
  removed.  In fact I was able to run the "brctl show" command as this
  was happening and see each tap device get put on a bridge before
  disappearing 1-2 seconds afterwards.  This output is also in the
  attachment.

  The one other observation I would note concerning the brctl output was
  that all the transient tap devices were being put on the same bridge:
  the one associated with VLAN 3 (eth1.3).  This should only have been
  the case for NIC1 (first NIC).  The other two should have each been on
  their own bridges / VLANs (eth1.6 and eth1.66).

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