Neutron agents process name changed after neutron-server setproctitle change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Unassigned |
Bug Description
In bug 1816485 we pushed code [0] to have nice process names for neutron-server workers (indicating RPC workers, ...). This was done via setproctitle.
Code itself does not affect other neutron components, but simply loading the setproctitle module will affect the process environment [1] in /proc/xx/environ.
This is quite visible when checking "ps -e" output, form:
# ps -e|grep neutron
4712 ? 00:00:02 neutron-openvsw
4775 ? 00:00:00 neutron-rootwra
4821 ? 00:00:02 neutron-dhcp-ag
4852 ? 00:00:01 neutron-l3-agen
4932 ? 00:00:00 neutron-rootwra
5790 ? 00:00:02 neutron-server
5844 ? 00:00:00 neutron-server
5845 ? 00:00:00 neutron-server
to:
# ps -e|grep neutron
28447 ? 00:00:00 neutron-rootwra
28805 ? 00:00:00 neutron-server:
28806 ? 00:00:00 neutron-server:
28807 ? 00:00:00 neutron-server:
31253 ? 00:00:00 neutron-rootwra
A shorter test, "ps -e | grep $(pgrep -f neutron-
Using setproctitle's SPT_NOENV feature to avoid clobbering does not work as proper environment name is the full "/usr/bin/python3.6 /usr/local/
While using other toosl (or ps options) to find the agent process work fine, some monitoring solutions only work on env name like "ps -e" output
As we added process names for neutron-
Bonus question: I wonder about backportability of such a fix, as it keeps old process name it should be mostly backwards-
[0] https:/
[1] https:/
[2] https:/
Changed in neutron: | |
importance: | Undecided → Low |
Changed in neutron: | |
assignee: | nobody → Bernard Cafarelli (bcafarel) |
Changed in neutron: | |
assignee: | Bernard Cafarelli (bcafarel) → Brian Haley (brian-haley) |
Changed in neutron: | |
assignee: | Brian Haley (brian-haley) → Bernard Cafarelli (bcafarel) |
Fix proposed to branch: master /review. opendev. org/735125
Review: https:/