Puppet users - Mar 2010 - Environment settings not functional

Hi,

I''ve got some problems with setting up environments. On the master:
[main]
[...]
manifestdir = /etc/puppet/manifests
modulepath = /etc/puppet/modules
[...]
environments = production,staging

[production]
manifestdir = /etc/puppet/manifests
modulepath = /etc/puppet/modules
[staging]
manifestdir = /opt/puppet-staging/manifests
modulepath = /opt/puppet-staging/modules

[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
storeconfigs = true
dbadapter = mysql
dbuser = puppet
dbpassword = X
dbserver = localhost
dbsocket = /var/lib/mysql/mysql.sock

-----------------------
Verify that the paths are correct:
# tree /opt/
/opt/
`-- puppet-staging
    |-- manifests
    |   `-- site.pp
    `-- modules
#cat /opt/puppet-staging/manifests/site.pp
node default {
        fail("Fail: Testing environments")
}
----------------
On the staging nodes, I''ve got this entry under [puppetd] in
puppet.conf:
environment = staging

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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

> 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

[root@dev-sandbox]puppetd --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

[root@dev-sandbox]puppetd --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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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 <somew...@gmail.com> 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
>
> [root@dev-sandbox]puppetd --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
>
> [root@dev-sandbox]puppetd --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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31/03/10 6:29 PM, Tore wrote:
> 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 :/
> 
What''s your user name?

Regards

James Turnbull

- -- 
Author of:
* Pro Linux System Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBS7MVCyFa/lDkFHAyAQK4gwgA2jpCOElB8AnWHr83FkfAIHNd//obMj0e
PpCXewbBOsIIos6upgxxRhn0PFEprHohTFHdXbad+DfhGRZAMjQ9GTxD40SEN926
bBxsPyIFt8TrlmTbTWkJjnrJPXLpL+twD/AVFCNZ5e7WRXycq9GGdUeIKGi0ke9v
nMx3Ukihff1FMNDzxS1zLlsUvNeRY7/8UmWOX0Vc+Na33bjGFMmZs6L6PPCqAsH1
VSa6WHPlHYy3vN+oMNtqaYGNdhEJR2HUnLymBJCW4atfOfcEOqtDN8tGI4lDfX4S
EPMS7uuHSQF/Vlr/SxtoeevOtg+EwWzfPwaxgVSSPBRU0hJTe3sNjw==bUYy
-----END PGP SIGNATURE-----

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