root@us01odc-qa-ctrl3:/var/log/neutron# cat /etc/sudoers.d/neutron_sudoers
Defaults:neutron !requiretty
neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf *
neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf
The errors appear to start with this line:
2019-10-10 13:42:48.261 1211336 ERROR neutron.agent.linux.utils [req-42c530f6-6e08-47c1-8ed4-dcb31c9cd972 - - - - -] Rootwrap error running command: ['iptables-save', '-t', 'raw']: Exception: Failed to spawn rootwrap process.
We¡¯re not running iptables. Do we need it, to use the rootwrap daemon?
From: Albert Braden <Albert.Braden@synopsys.com>
Sent: Thursday, October 10, 2019 12:13 PM
To: Erik Olof Gunnar Andersson <eandersson@blizzard.com>; Chris Apsey <bitskrieg@bitskrieg.net>
Cc: openstack-discuss@lists.openstack.org
Subject: RE: Port creation times out for some VMs in large group
It looks like something is still missing. I added the line to /etc/sudoers.d/neutron_sudoers:
root@us01odc-qa-ctrl3:/var/log/neutron# cat /etc/sudoers.d/neutron_sudoers
Defaults:neutron !requiretty
neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf *
neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf *
Then I restarted neutron services and the error was gone¡¦ for a few minutes, and then it came back on ctrl3. Ctrl1/2 aren¡¯t erroring at this time. I changed neutron¡¯s shell and tested the daemon command and it seems to work:
root@us01odc-qa-ctrl3:~# su - neutron
neutron@us01odc-qa-ctrl3:~$ /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf
/tmp/rootwrap-5b1QoP/rootwrap.sock
Z%¢Æ"¢Æ¢Æ¢ÆVs¢Æ¢Æ5-¢Æ,a¢Æ¢Æ¢Æ¢ÆG¢Æ¢Æ¢Æ¢Æv¢Æ¢Æ
But neutron-linuxbridge-agent.log still scrolls errors:
http://paste.openstack.org/show/782740/
It appears that there is another factor besides the config, because even when the sudoers line was missing, it would work for hours or days before the error started. It has been working in our prod cluster for about a week now, without the sudoers line. It seems like it should not work that way. What am I missing?