lbaasv2 namespace missing host routes from VIP subnet
Bug #1541802 reported by
Damien Churchill
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
Medium
|
Unassigned |
Bug Description
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-
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.
tags: | added: lbaas |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → yaowei (yaowei) |
affects: | neutron → octavia |
To post a comment you must log in.
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.