openvswitch-agent spawning infinite number of ovsdb-client processes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Wishlist
|
Unassigned |
Bug Description
After installing neutron on Ubuntu Xenial from the Newton UCA (2:9.0.
neutron 11222 2.9 0.8 262628 108712 ? Ss 10:59 1:36 /usr/bin/python /usr/bin/
root 11686 0.0 0.0 54112 3256 ? S 11:00 0:00 \_ sudo neutron-rootwrap /etc/neutron/
root 11688 0.0 0.3 83336 45444 ? S 11:00 0:00 | \_ /usr/bin/python /usr/bin/
root 11828 0.0 0.0 20056 2976 ? S 11:00 0:00 | \_ /usr/bin/
root 13426 0.0 0.0 54112 3204 ? S 11:00 0:00 \_ sudo neutron-rootwrap /etc/neutron/
root 13430 0.0 0.3 83336 45480 ? S 11:00 0:00 | \_ /usr/bin/python /usr/bin/
root 13490 0.0 0.0 20056 3052 ? S 11:00 0:00 | \_ /usr/bin/
root 14775 0.0 0.0 54112 3256 ? S 11:01 0:00 \_ sudo neutron-rootwrap /etc/neutron/
root 14779 0.0 0.3 83336 45272 ? S 11:01 0:00 | \_ /usr/bin/python /usr/bin/
root 14821 0.0 0.0 20056 2944 ? S 11:01 0:00 | \_ /usr/bin/
with another set being spawned every 30 seconds. In /var/log/
2017-01-20 11:00:39.804 11222 ERROR neutron.
2017-01-20 11:00:39.805 11222 ERROR neutron.
Now of course one can claim that properly setting up sudo (or /etc/hosts rather) will solve this issue, but still maybe the ovs-agent process should properly clean up its children and not assume that they are dead as soon as there is any output to stderr (function _read_stderr() in neutron/
tags: | added: ovs |
Changed in neutron: | |
importance: | Undecided → Wishlist |