To answer a part of my own question:
dnsmasq is running on the controller node because there is a libvirt service
running. Which got installed as a dependency of the
Virtualization host package group… so no one to blame but myself.
Am 12.06.2015 um 14:07 schrieb Uwe Sauter:
Gary,
Thanks.
And to answer the second part of my question:
This all seems to be related to SElinux. From /var/log/neutron/dhcp-agent.log:
2015-06-12 14:31:58.757 7130 ERROR neutron.agent.linux.utils [-]
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip',
'netns', 'exec',
Gary,
Thanks.
That brings up the question why there are dnsmasq processes running on my
controller node (which has neutron-server running) and
not on the networking node (neutron-dhcp-agent neutron-l3-agent
neutron-metadata-agent neutron-openvswitch-agent).
Any suggestions?
Regards,
Hi,
== TL;DR ==
Which neutron service manages the DNSMASQ processes? Does this run on the
controller node or the networking node?
== Long story ==
I have a five node Juno installation (1 controller, 1 storage, 1 network and 2
compute nodes).
I followed the Juno Red Hat installation guide [1]
Hi,
The DHCP agent runs the dnsmasq process. That is done on the network node.
Thanks
Gary
On 6/12/15, 2:35 PM, Uwe Sauter uwe.sauter...@gmail.com wrote:
Hi,
== TL;DR ==
Which neutron service manages the DNSMASQ processes? Does this run on the
controller node or the networking node?
== Long
