yahoo-eng-team team mailing list archive

[Diego Lima <diegolima.br@xxxxxxxxx>]

Public bug reported:

Neutron load balancer namespaces do not inherit any settings on their
subnets, including custom routes, since it does not use DHCP to
configure its interface. Users expect that load balancers are able to
reach the same networks their instances do.

To reproduce the problem take the following steps:

1 - Create a subnetwork
2 - Create 2 routers connecting to different networks
3 - Edit the subnetwork and add some custom routes using the second router
4 - Launch an instance. It should receive the custom routes via DHCP and reach them through the second router.
5 - Create a load balancer
6 - Check the load balancer's namespace routing table. There will be no custom routes.


This is related to https://bugs.launchpad.net/neutron/+bug/1376446,
although its a different bug. As a workaround an user can create a
second subnet which use the second router as its default gateway and
place the load balancers there.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: lbaas

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

Title:
  Neutron LBAAS agent do not use custom routes configured on their
  subnet

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Neutron load balancer namespaces do not inherit any settings on their
  subnets, including custom routes, since it does not use DHCP to
  configure its interface. Users expect that load balancers are able to
  reach the same networks their instances do.

  To reproduce the problem take the following steps:

  1 - Create a subnetwork
  2 - Create 2 routers connecting to different networks
  3 - Edit the subnetwork and add some custom routes using the second router
  4 - Launch an instance. It should receive the custom routes via DHCP and reach them through the second router.
  5 - Create a load balancer
  6 - Check the load balancer's namespace routing table. There will be no custom routes.


  This is related to https://bugs.launchpad.net/neutron/+bug/1376446,
  although its a different bug. As a workaround an user can create a
  second subnet which use the second router as its default gateway and
  place the load balancers there.

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