yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2052681@xxxxxxxxxxxxxxxxxx>]

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.


** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2052681

Title:
  Many stale neutron-keepalived-state-change processes left after
  upgrade to native pyroute2 state-change

Status in neutron:
  Invalid

Bug description:
  Needs a post-upgrade script to remove those stale "ip -o monitor" and
  traditional "neutron-keepalived-state-change" processes.

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