← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1410951] Re: Devstack does not set the "gateway_external_netword_id" to null when "external_network_bridge" is set to null. They both should be set to null in the l3_agent.ini when a single agent supports multiple external network

 

** Project changed: neutron => devstack

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

Title:
  Devstack does not set the "gateway_external_netword_id" to null when
  "external_network_bridge" is set to null. They both should be set to
  null in the l3_agent.ini when a single agent supports multiple
  external network

Status in devstack - openstack dev environments:
  New

Bug description:
  When multiple external networks are set for the provider network, the
  l3_agent.ini should have

  external_network_bridge = ""
  gateway_external_network_id = ""

  if a single agent is hosting all the multiple external networks.

  In devstack today, when there is no 'br-ex' configured, the devstack
  "stack.sh" script only configures external_network_bridge="" and not
  gateway_external_network_id.

  This  causes some issues in validation. Because there is a check to
  make sure if the "gateway_external_network" is null or not. If the key
  is not found, the action varies.

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


References