Comment 2 for bug 2052681

Hello:

I've tested with an older version of Neutron (Stein) and the problem you are describing is not related to the new implementation of "neutron-keepalived-state-change" process, but how this process was stopped.

The "ip -o monitor" processes are child processes of "neutron-keepalived-state-change" and are (should be) stopped when "neutron-keepalived-state-change" is. If the process is killed, the child processed won't be correctly stopped. If the "neutron-keepalived-state-change" is started again (with the old or the new implementation), the "ip -o monitor" leftovers will remain in the system.

Please check how are you stopping the "neutron-keepalived-state-change" processes and how are you upgrading your system.

Regards.