-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds the Proxy User to the 'puppet' Group when Not Present #295
Comments
this will probably require a larger refactoring... I also wonder how the ssl certificate stuff is handled now, when puppet-agent doesn't create the user/group anymore... |
My setup is that I have a single machine running Foreman and the proxy, with the proxy only managing a DHCP and TFTP server on the same machine. My Puppet Server, CA, and DB are all remote hosts, as is BIND. |
@rfkrocktk while for this specific usecase there solution might be an easy one, the underlying problem is a deeper one, as there are quite some places where the existence of a "puppet" group is just assumed. |
Is the issue #341 the same ? I think we should just add a puppet user/group to an Puppet 4 AIO install and chown -R puppet:puppet /etc/puppetlabs/puppet/ssl to it and add the foreman-proxy group to it. I did this manually earlier as I remember and that works and won't break a thing in the future as well. |
As far as I can see the AIO package is not detected right and the puppet_home is not set accordingly to it. Can someone please check this ? |
Doesn't e12a382 solve this? |
@ekohl: I am still having this problem with smart proxy 1.17 and puppet 5. My command line for the installer is the following (plus additional parameter for oauth and other environment specific parameters):
So it should go into the condition |
This line causes
foreman_proxy::groups
to always include thepuppet
group, regardless of whetherforeman_proxy::puppet
is true or false. This breaks things:The text was updated successfully, but these errors were encountered: