haproxy-lbaas-agent goes out of sync with db after being down
Bug #1262885 reported by
Simon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Oleg Bondarev |
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.
Changed in neutron: | |
assignee: | nobody → Oleg Bondarev (obondarev) |
Changed in neutron: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Apparently you mean that haproxy process will remain. That's correct.
Agent has no knowledge of running haproxy processes unless it knows pool id, but it doesn't know it because the pool was deleted during the downtime.
The only option would be to scan state path for certain directories, parse ids and kill corresponding processes.