HAProxy LBaaS driver does not work with L3 HA

[Abhishek Chanda]

We have a deployment with L3 HA. When we deployed HAProxy LBaaS driver on it, a few times, the haproxy instance landed on a network node that was not the master. When this happens, there is no way to access the load balanced instances over a floating IP. Here are the steps:

1. Deploy neutron with L3 HA and HAProxy LBaaS driver.
2. Setup a tenant and a public network with a HA router for the public network.
3. Boot three VMs in the tenant network.
4. Create a lb pool.
5. Add two VMs to the pool.
6. Create a health monitor and associate to the pool.
7. Create a VIP.
8. Start servers on the two VMs.
9. Create a floating IP in neutron.
10. Associate the floating IP to the VIP.

At this point, the servers should be accessible from outside the cloud using the floating IP. But that does not happen if the haproxy instance is scheduled on a node that is not the master in L3 HA.

[Sadique (sadiqueklr)]

I haven't come across this issue during my testing. I have my lbaas instance running on one of the node and the floating ip is on a different node's qrouter interface with l3-ha.

BTW, do you have l2population enabled?

[venkata anil (anil-venkata)]

I also couldn't reproduce this issue. Lbaas VIP port is like any other neutron port. So if a neutron port(even for LBaaS VIP port) is not in the HA master node and having a floating IP, then should be able to be reached from external network.
Unassigning myself as I couldn't reproduce it.

[venkata anil (anil-venkata)]

l2population should be disabled if you are using L3 HA.

[Launchpad Janitor (janitor)]

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