manifest setting in puppet.conf does not work

[Axel Bock]

Hello readers,

I am configuring my environment to have a separate manifest file, using $environment to in the module and manifest path.
For the modules it works now. The site.pp file ... is another issue. I was under the impression it did, but it wasnt.

Basically I did the following:

modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/modules
manifest = /etc/puppet/environments/$environment/site.pp:/etc/puppet/manifests/site.pp

now when I define a node within an environment _only_ and not within the global site.pp file, It runs - but applies an empty catalog. When I move the node definition to the global site.pp file in /etc/puppet/manifests/site.pp, it works again. The very same defnition, just copied from one file to another. It also does not work when I use single-file/single-directory entries for modulepath and manifest.


Any ideas here? I could use some :)
Thanks & greetings!
Axel.

[Axel Bock]

hm, since no one here seems to have an idea - maybe someone can answer me another question related to this:

is there a "debug" mode on the puppet MASTER? this way I could maybe figure out what the master does and "thinks", and why he does not obey my little manifest setting.


thanks & cheers!
Axel.

[Andreas Paul]

I have the same problem, but the other way around :)
My puppet client only uses the node definitions in the environment specific site.pp

Anyway you can debug the master with:

puppet master --verbose --no-daemonize --debug

[Axel Bock]

ha, let's combine our problems and we have either a puppet master using NO definition, or a working system ;)
thanks for the debug line :)

greetings,
axel.

[jcbollinger]

On Monday, September 24, 2012 6:48:56 AM UTC-5, Axel Bock wrote:

Any ideas here? I could use some :)

I don't have any specific advice about this problem, but on general principles you may want to look at which section of your puppet.conf contains those settings.  Behavior may differ depending on whether they appear in [main] or in [master].


John

[Peter]

Hi Axel,

I had a similar issue checkout - https://groups.google.com/d/topic/puppet-users/C5Pfg_r_Srs/discussion

 

I am not positive however I believe your issue likely falls fowl of the same problem I had, essentially the manifest directive only takes a single file location.

 

Peter.

[Axel Bock]

Hi Peter, hi John,

first: Thanks, putting the setting in [master] actually did something - and overriding the commandline setting from SuSE linux ;) .
right now I am using ...<path>/$environment.pp as manifest file, which works beautifully.

and yes, it seems manifest only takes a single file as parameter. (makes sense if you think of it - if you define a host two times, which one is taken?)


thanks a lot & greetings,
axel.