If there is a /var/lib/neutron/ha_confs/<router-id>.pid then l3 agent fails to spawn a keepalived process for that router
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Hynek Mlnarik | ||
Kilo |
New
|
Undecided
|
Unassigned |
Bug Description
If the .pid file for the previous keepalived process (located in /var/lib/
For example, upon neutron node shutdown and restart the processes are assigned new PIDs that can be same as those previously assigned to some of the keepalived processes. The latter are captured in PID files and once keepalived starts, it detects that there is a running process with that PID and reports "daemon is already running".
Steps to reproduce:
1) Pick a router that you want to make display this issue; record the router_id
2) kill the two processes denoted in these two files: /lib/neutron/
3) Make sure that no keepalived process comes back for this router
4) Now pick out an existing process id - anything that's really running - and put that processid into the PID files. For example, a background sleep process running as pid 12345 can be put into <router_id>.pid file and <router_
Bug valid with keepalived version 1.2.13 and 1.2.19.
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Fix proposed to branch: master /review. openstack. org/296532
Review: https:/