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

[Diego Lima]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/144931

[OpenStack Infra (hudson-openstack)]

Change abandoned by Kyle Mestery (<email address hidden>) on branch: master
Review: https://review.openstack.org/144931
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Armando Migliaccio (armando-migliaccio)]

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]