Project

General

Profile

Actions

Bug #3273

closed

mco puppet run should set as arguments the puppet ca and puppet master

Added by cristian falcas over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.

Actions #1

Updated by Dominic Cleal over 10 years ago

  • 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.

Actions #2

Updated by cristian falcas over 10 years ago

I understand, thank you.

Actions #3

Updated by cristian falcas over 10 years ago

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.

Actions #4

Updated by Dominic Cleal over 10 years ago

  • 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.

Actions #5

Updated by cristian falcas over 10 years ago

Yes, the environment is authoritative, but the other selections (master and CA) are not. And I was pointing out that this is not consistent.

Actions #6

Updated by Dominic Cleal over 10 years ago

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.

Actions #7

Updated by cristian falcas over 10 years ago

I started doing this. Thank you for your time.

Actions #8

Updated by Dominic Cleal over 10 years ago

  • Status changed from Feedback to Resolved

No problem!

Actions

Also available in: Atom PDF