Loading...

puppet-users@googlegroups.com

[Prev] Thread [Next]  |  [Prev] Date [Next]

[Puppet Users] Re: Environment settings not functional Tore Wed Mar 31 01:00:14 2010

Hi,

Thanks, I needed to add the `manifest' option to my puppmaster under
[main] and [staging]. I removed [production] all together.

Notice, that output from the client node always showed manifestdir to
be /etc/puppet/manifests:
#puppetd --test --debug --environment staging-- configprint
environment,manifestdir
> environment = staging
> manifestdir = /etc/puppet/manifests

I wish I could update the documentation on the wiki, but for some
reason Redemi believes I've allready got an registered account, but
I'm not able to log in with OpenID :/

Thanks alot!

On 30 Mar, 17:45, deet <[EMAIL PROTECTED]> wrote:
> > On the staging nodes, I've got this entry under [puppetd] in
> > puppet.conf:
> > environment = staging
>
>   Tore.
>
> To get environments working I had to include modulepath, manifest and
> manifestdir under each enviroment in puppet.conf.   For example my
> testing stanza from the client puppet.conf looks like this
>
> [testing]
>     modulepath  = /etc/puppet-test/modules
>     manifest    = /etc/puppet-test/manifests/site.pp
>     manifestdir = /etc/puppet-test/manifests
>
>  I've found the "configprint" command line argument a necessity to get
> environments working.
>
>  For example before I included manifestdir in my client node
> puppet.conf I saw this
>
> [EMAIL PROTECTED] --test --debug --environment testing --
> configprint environment,manifestdir
> environment = testing
> manifestdir = /etc/puppet/manifests
>
>  Then when I added the manifestdir in puppet.conf everything was happy
>
> [EMAIL PROTECTED] --test --debug --environment testing --
> configprint environment,manifestdir
> environment = testing
> manifestdir = /etc/puppet-test/manifests
>
>  I'm not an expert at environments and it took me awhile to realize
> that I needed the client side puppet.conf configurations and that the
> command line flag "--environment" was not enough to indicate which
> environment to use.
>
>   Try playing with your clients puppet.conf and running with
> configprint to see if that provides more insight into what's
> happening.
>
>   HTH.  Derek.
>
>
>
> > But, the nodes are still directed to the default environment under /
> > etc/puppet/ {manifests, modules}. Even if I exectued puppetd manually
> > it wont work:
> > # puppetd --verbose --no-daemonize --environment=staging
> > notice: Starting Puppet client version 0.25.4
> > info: Caching catalog for X
> > info: Applying configuration version '1269955369'
> > notice: Finished catalog run in 0.01 seconds
> > notice: Caught INT; calling stop
>
> > Have no idea what to try now, any suggestions?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.