Comment 3 for bug 2052681

Hi,

@Rodolfo, thank you for the tests. So, IMO, you reproduced the issue.

"How to do the upgrade? And how to stop the traditional neutron-keepalived-state-change processes?", IMHO, these should be the part of the pyroute2 implementation work. We should update the DOC for users to tell them how to upgrade, or warn the this such upgrade issue, while we do not cover the upgrade tools or stop the processes automatically and implicitly.

So, let's find the answer about the question, how to upgrade or stop the process ?
A simple kill "<pid of ip -o monitor>" and "<pid of neutron-keepalived-state-change>" is fine to work? It has a sequences here, IMO, pkill -f "ip -o monitor" should be run first, and then pkill -f neutron-keepalived-state-change. These commands should be run one by one on all l3-agent hosts.

Another issue I noticed is that, the new pyroute2 implementation changed the PID file name from:
<router_id>.monitor.pid
to
<router_id>.monitor.pid.neutron-keepalived-state-change-monitor

So, after upgrade, neutron-l3-agent will start new "neutron-keepalived-state-change" for all routers because the new pid file is empty. Then all traditional neutron-keepalived-state-change and the ip -o monitor process remain.

Please confirm this.