yahoo-eng-team team mailing list archive

[Alan Pevec <1234750@xxxxxxxxxxxxxxxxxx>]

** Also affects: neutron/havana
   Importance: Undecided
       Status: New

** Changed in: neutron/havana
       Status: New => Fix Committed

** Changed in: neutron/havana
    Milestone: None => 2013.2.4

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

Title:
  multiple external networks

Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in neutron havana series:
  Fix Committed

Bug description:
  I have multiple external networks, and therefore each l3-agent is
  running with a particular ext network ID.

  When I create a lrouter, which is scheduled to be on one l3-agent
  randomly. If I set the ext-gw for that lrouter later on to be an
  external network different from the ext-net the l3-agent is on, the
  entire lrouter somehow goes down, both internal and external
  interfaces.

  I would prefer to see:
  1) the operation of putting the lrouter onto the "wrong" ext-net is disallowed;
  2) or better, we can move the lrouter to the right l3-agent with the correct ext-net.

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