yahoo-eng-team team mailing list archive

[Abhishek Chanda <abhishek@xxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  HAProxy LBaaS driver does not work with L3 HA

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  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.

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