Bug #3273
closed
mco puppet run should set as arguments the puppet ca and puppet master
Added by cristian falcas over 11 years ago.
Updated over 11 years ago.
Category:
Puppet integration
|
Description
I have 1 puppet ca server and 2 puppet masters. I edited the host and selected a CA server and a master server.
When I execute a puppet run via "Run puppet", the puppet agent will be executed by mco with the default ca server and puppet master.
I'm not sure if this is a mco issue, or a foreman issue, or if it's an issue at all. But I was expecting that the run will respect the definition of the host.
- Category set to Puppet integration
Normally this is achieved by templating the puppet.conf file on the host itself. When a host is provisioned, we use the puppetmaster settings in the provisioning template to generate puppet.conf, but we don't maintain this file on an ongoing basis (you could do with our 'puppet' module).
I think setting up ongoing management of puppet.conf is preferable to passing the server arguments via the run puppet mechanism.
I still want to say that this is not consistent with the environment selection: the value from foreman is overwriting the one set in puppet agent conf file.
- Status changed from New to Feedback
The environment selection in Foreman should be authoritative too, unless you disable the enc_environment setting as it gets passed to Puppet in the ENC output. Puppet 2.x wasn't good at following it, but Puppet 3.x will reliably.
Yes, the environment is authoritative, but the other selections (master and CA) are not. And I was pointing out that this is not consistent.
So I think the way to do this is to manage your puppet.conf on an ongoing basis - using puppet. You can use our "puppet" module (https://github.com/theforeman/puppet-puppet/) which will use the puppetmaster value from the ENC to fill in the "server" config line, just add it to a base host group.
I started doing this. Thank you for your time.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF