>
> I was wondering if the user/group should be (only) set in a common config,
> like neutron.conf, if it should be duplicated in dhcp and metadata config
> files, or if the metadata ini should be added to the list of ini files,
> when starting up the DHCP agent.
>
Previously, metadata_proxy_user/
Yeah, the setting for user was neutron. The setting for group was different
than the process that started up the proxy (which had user neutron and
group neutron). The review 161494, was it applied to Liberty?
I think in our case, DHCP agent only had dhcp ini file and not metadata ini
file, so it d
Hi,
Are you sure metadata_proxy_user==neutron?
neutron-metadata-proxy must be able to connect to the metadata-agent socket
and watchs its log files and neutron user should be able to do both with
usual file permissions.
Otherwise the metadata proxy is generally no more able to:
- watch log[1] so
Hi,
I had seen something and was not sure if this was a subtle bug or not.
I have a Liberty based openstack setup. The account that is setting up
processes was user=neutron, group=neutron, however the metadata_agent.ini
config file was set up for a different group. So there was a
metadata_proxy_u
