I have the neutron sudoers line under sudoers.d:

root@us01odc-qa-ctrl1:/etc/sudoers.d# cat neutron_sudoers

Defaults:neutron !requiretty

neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf *

Whatever is causing this didn’t start until I had been running the rootwrap daemon for 2 weeks, and it has not started in our prod cluster.

From: Erik Olof Gunnar Andersson <eandersson@blizzard.com>
Sent: Wednesday, October 9, 2019 6:40 PM
To: Albert Braden <albertb@synopsys.com>; Chris Apsey <bitskrieg@bitskrieg.net>
Cc: openstack-discuss@lists.openstack.org
Subject: Re: Port creation times out for some VMs in large group

You are probably missing an entry in your sudoers file.

You need something like

neutron ALL = (root) NOPASSWD: /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf

---

From: Albert Braden <Albert.Braden@synopsys.com>
Sent: Wednesday, October 9, 2019 5:20 PM
To: Chris Apsey <bitskrieg@bitskrieg.net>
Cc: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Subject: RE: Port creation times out for some VMs in large group

We tested this in dev and qa and then implemented in production and it did make a difference, but 2 weeks later we started seeing an issue, first in dev, and then in qa. In syslog we see neutron-linuxbridge-agent.service stopping and starting[1]. In neutron-linuxbridge-agent.log we see a rootwrap error[2]: “Exception: Failed to spawn rootwrap process.”

If I comment out ‘root_helper_daemon = "sudo /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf"’ and restart neutron services then the error goes away.

How can I use the root_helper_daemon setting without creating this new error?

http://paste.openstack.org/show/782622/