Comment 7 for bug 1332544

Hi,

In Debian, I have now added a chmod o+x /var/lib/neutron, which seems to fix the issue. However, the question is still pending: should neutron set user=neutron when starting dnsmasq?

FYI, the patch would be to add:

--user=neutron

in neutron/agent/linux/dhcp.py, in the spawn_process() method. I know that at least the Debian DSA are doing this (by patching the dhcp.py file manually), and it worked well. Note that I've raised the issue in the dev list, with no answer from anyone in Neutron.

Cheers,

Thomas