lbaasv2 namespace missing host routes from VIP subnet

[Damien Churchill]

When a lbaasv2 namespace is created it only receives the default gateway for that subnet, the additional host routes defined against the subnet are ignored which results in certain areas of a network being inaccessible.

# ip netns exec qlbaas-ae4b71ef-e874-46a1-a489-c2a6e186ffe3 ip r s
default via 192.168.31.254 dev tap9e9051cd-ff
192.168.31.0/24 dev tap9e9051cd-ff proto kernel scope link src 192.168.31.48

Version Info:

OpenStack: Liberty
Distro: Ubuntu 14.04.3

Not sure if any more information is required.

[Brandon Logan (brandon-logan)]

this is for the v2 agent namespace driver.

looking at the code here:

https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/drivers/haproxy/namespace_driver.py#L314-L319

Looks like if the subnet has no gateway then it'll use the host routes. If it does have a gateway then it will not configure the host routes.

[Brandon Logan (brandon-logan)]

This looks like a bug to me because the host routes can be extra routes to take besides the default gateway ip.

It would need to be added here after this line:

https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/drivers/haproxy/namespace_driver.py#L323

[Gregory Thiemonge (gthiemonge)]

Abandoned after re-enabling the Octavia launchpad.