While the below bugs describe similar symptoms, they describe the case where the privsep daemon is forked from the client process
https://bugs.launchpad.net/oslo.privsep/+bug/1887506 https://bugzilla.redhat.com/show_bug.cgi?id=1862364
while in our case it gets started via the /usr/bin/privsep-helper script in a child process:
CGroup: /system.slice/neutron-openvswitch-agent.service ├─108898 /usr/bin/python3 /usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/openvswitch_age └─109233 /usr/bin/python3 /usr/bin/privsep-helper --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --pr
While the below bugs describe similar symptoms, they describe the case where the privsep daemon is forked from the client process
https:/ /bugs.launchpad .net/oslo. privsep/ +bug/1887506 /bugzilla. redhat. com/show_ bug.cgi? id=1862364
https:/
while in our case it gets started via the /usr/bin/ privsep- helper script in a child process:
CGroup: /system. slice/neutron- openvswitch- agent.service neutron- openvswitch- agent --config- file=/etc/ neutron/ neutron. conf --config- file=/etc/ neutron/ plugins/ ml2/openvswitch _age privsep- helper --config-file /etc/neutron/ neutron. conf --config-file /etc/neutron/ plugins/ ml2/openvswitch _agent. ini --pr
├─108898 /usr/bin/python3 /usr/bin/
└─109233 /usr/bin/python3 /usr/bin/