search

theforeman / puppetdb_foreman

PuppetDB proxy in Foreman
http://theforeman.org
GNU General Public License v3.0
32 stars 23 forks source link

Still being maintained? #69

Closed metalcated closed 3 years ago

metalcated commented 3 years ago

Is this still being maintained? And will there be support added for Foreman version 2+? Thanks

timogoebel commented 3 years ago

@metalcated: Does this imply, that this plugin does not work for Foreman 2.0 + ?

metalcated commented 3 years ago

I am not sure if it's a change on the Puppet end or if something needs to change here, but I did notice that the private key is unable to be read by this plugin and thus an error is thrown in the foreman UI "permission denied." One you set the permissions to something unsafe for a private key (644), the plugin works again and I no longer receive a permissions error.

Sorry about the delay in my response.

laugmanuel commented 3 years ago

@metalcated , which path do you use for the private key? If you are using the default Puppet key dir (/etc/puppetlabs/puppet/ssl/private_keys/) this is just a limitation of file system permissions as Foreman is ran with the foreman user by default.

We use some custom Puppet code which copies the Puppet private key to a different location and sets the permissions and owner/group accordingly. Then we use this file for the plugin.

timogoebel commented 3 years ago

@metalcated: To answer your original question: Yes. This plugin is still being maintained.

metalcated commented 3 years ago

Yes this is the exact error:

Oops, we're sorry but something went wrong Permission denied @ rb_sysopen - /etc/puppetlabs/puppet/ssl/private_keys/fqdn.pem

I did add the foreman user to the puppet group but didn't restart the services. That could be the gotcha. I will update shortly if that fixes my issue.

metalcated commented 3 years ago

Yep, that seemed to work. Thanks all.