yahoo-eng-team team mailing list archive

[Simon <1262885@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

How to reproduce:

1) create a pool with a VIP
2) check which lbaas-agent that pool is scheduled to
3) shut down lbaas-agent on the node
4) remove the pool/VIP via the API
5) restart lbaas-agent

It turns out the VIP would remain on the lbaas-agent host forever.

Looks like the instance_mapping variable is reset to empty restart the
agent restarted, so it essentially lost track of that removed pool/vip.

** 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/1262885

Title:
  haproxy-lbaas-agent goes out of sync with db after being down

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  How to reproduce:

  1) create a pool with a VIP
  2) check which lbaas-agent that pool is scheduled to
  3) shut down lbaas-agent on the node
  4) remove the pool/VIP via the API
  5) restart lbaas-agent

  It turns out the VIP would remain on the lbaas-agent host forever.

  Looks like the instance_mapping variable is reset to empty restart the
  agent restarted, so it essentially lost track of that removed
  pool/vip.

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