Re: [Puppet Users] Can't get puppet/passenger to stop using /home/puppet/.puppet
Added info.
When I look in /var/log/syslog I see the line
puppet-master[26751]: Using settings: adding file resource '*confdir*':
'File[/home/puppet/.puppet]{:ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false, :path=>"/home/puppet/.puppet"}'
My config.ru file contains the line
ARGV << "--confdir" << "/etc/puppet"
but it appears to me that my directive is being ignored.
Since syslog is indicating the creation of /home/puppet.puppet for confdir
it is as if either my config.ru file isn't being read, or the --confdir
argument in config.ru is being ignored. I'm pretty certain it is actually
reading the file because I added ARGV << "--debug" to config.ru and when I
run things again I am seeing debug messages in syslog. So it appears the
config.ru is being read.
On Fri, Apr 11, 2014 at 8:35 AM, John Pyeatt wrote:
> Yes. puppet has those permissions.
> I even tried doing
>
> chown -R puppet:puppet /etc/puppet
> and
> chown -R puppet:puppet /usr/share/puppet
>
>
>
>
> On Thu, Apr 10, 2014 at 5:30 PM, Spencer Krum wrote:
>
>> Does the puppet user have read/execute on all files/dirs under
>> /etc/puppet?
>>
>> Is the config.ru file owned by the puppet user?
>>
>>
>> On Thu, Apr 10, 2014 at 3:21 PM, John Pyeatt
>> wrote:
>>
>>> I've followed all of the documentation at
>>> http://docs.puppetlabs.com/guides/passenger.html to try to switch from
>>> webrick to passenger/apache.
>>>
>>> I'm obviously doing something wrong however because I can't get
>>> passenger to use /etc/puppet instead of /home/puppet/.puppet to store data.
>>>
>>> Any ideas would be appreciated. Below are some of the details.
>>>
>>> I'm running it on Ubuntu 12
>>> I'm using Apache 2.2.22
>>> I'm using puppet 3.4.0
>>> I'm using passenger 4.0.41
>>>
>>> 1) I've created the directories /usr/share/puppet/rack/puppetmasterd
>>> with ./public ./tmp directories
>>>
>>> 2) In that directory I've put in a config.ru that looks like this:
>>> # a config.ru, for use with every rack-compatible webserver.
>>> # SSL needs to be handled outside this, though.
>>> # if puppet is not in your RUBYLIB:
>>> # $:.unshift('/var/lib/puppet')
>>> $0 = "master"
>>> # if you want debugging:
>>> # ARGV << "--debug"
>>> ARGV << "--rack"
>>>
>>>
>>> *ARGV << "--confdir" << "/etc/puppet"ARGV << "--vardir" <<
>>> "/var/lib/puppet"*require 'puppet/application/master'
>>> # we're usually running inside a Rack::Builder.new {} block,
>>> # therefore we need to call run *here*.
>>> run Puppet::Application[:master].run
>>>
>>> 3) I've created the file /etc/apache2/sites-available/passenger with the
>>> following snippet
>>> DocumentRoot */usr/share/puppet/rack/puppetmasterd/public*
>>>
>>>
>>> Options None
>>> AllowOverride None
>>> # Apply the right behavior depending on Apache version.
>>> Order allow,deny
>>> Allow from all
>>>
>>>
>>> No matter what I've tried it still puts everything to
>>> /home/puppet/.puppet directory instead of using /etc/puppet
>>>
>>>
>>>
>>>
>>>
>>> --
>>> John Pyeatt
>>> Singlewire Software, LLC
>>> www.singlewire.com
>>> --
>>> 608.661.1184
>>> john.pye...@singlewire.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/CAEisTLk4w%2BJJN5GvgBz%3DNA8%2BTTcfQ49ZCD0AABdU2E-mCBhQNw%40mail.gmail.com<https://groups.google.com/d/msgid/puppet-users/CAEisTLk4w%2BJJN5GvgBz%3DNA8%2BTTcfQ49ZCD0AABdU2E-mCBhQNw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Spencer Krum
>> (619)-980-7820
>>
>> --
>> Yo
Re: [Puppet Users] Can't get puppet/passenger to stop using /home/puppet/.puppet
Yes. puppet has those permissions.
I even tried doing
chown -R puppet:puppet /etc/puppet
and
chown -R puppet:puppet /usr/share/puppet
On Thu, Apr 10, 2014 at 5:30 PM, Spencer Krum wrote:
> Does the puppet user have read/execute on all files/dirs under
> /etc/puppet?
>
> Is the config.ru file owned by the puppet user?
>
>
> On Thu, Apr 10, 2014 at 3:21 PM, John Pyeatt
> wrote:
>
>> I've followed all of the documentation at
>> http://docs.puppetlabs.com/guides/passenger.html to try to switch from
>> webrick to passenger/apache.
>>
>> I'm obviously doing something wrong however because I can't get passenger
>> to use /etc/puppet instead of /home/puppet/.puppet to store data.
>>
>> Any ideas would be appreciated. Below are some of the details.
>>
>> I'm running it on Ubuntu 12
>> I'm using Apache 2.2.22
>> I'm using puppet 3.4.0
>> I'm using passenger 4.0.41
>>
>> 1) I've created the directories /usr/share/puppet/rack/puppetmasterd with
>> ./public ./tmp directories
>>
>> 2) In that directory I've put in a config.ru that looks like this:
>> # a config.ru, for use with every rack-compatible webserver.
>> # SSL needs to be handled outside this, though.
>> # if puppet is not in your RUBYLIB:
>> # $:.unshift('/var/lib/puppet')
>> $0 = "master"
>> # if you want debugging:
>> # ARGV << "--debug"
>> ARGV << "--rack"
>>
>>
>> *ARGV << "--confdir" << "/etc/puppet"ARGV << "--vardir" <<
>> "/var/lib/puppet"*require 'puppet/application/master'
>> # we're usually running inside a Rack::Builder.new {} block,
>> # therefore we need to call run *here*.
>> run Puppet::Application[:master].run
>>
>> 3) I've created the file /etc/apache2/sites-available/passenger with the
>> following snippet
>> DocumentRoot */usr/share/puppet/rack/puppetmasterd/public*
>>
>>
>> Options None
>> AllowOverride None
>> # Apply the right behavior depending on Apache version.
>> Order allow,deny
>> Allow from all
>>
>>
>> No matter what I've tried it still puts everything to
>> /home/puppet/.puppet directory instead of using /etc/puppet
>>
>>
>>
>>
>>
>> --
>> John Pyeatt
>> Singlewire Software, LLC
>> www.singlewire.com
>> --
>> 608.661.1184
>> john.pye...@singlewire.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CAEisTLk4w%2BJJN5GvgBz%3DNA8%2BTTcfQ49ZCD0AABdU2E-mCBhQNw%40mail.gmail.com<https://groups.google.com/d/msgid/puppet-users/CAEisTLk4w%2BJJN5GvgBz%3DNA8%2BTTcfQ49ZCD0AABdU2E-mCBhQNw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Spencer Krum
> (619)-980-7820
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CADt6FWPQb%2BoqwzzYBGyi1Yu1r%2B4s8oT7Y1TOn_8t_u7Xaix8ow%40mail.gmail.com<https://groups.google.com/d/msgid/puppet-users/CADt6FWPQb%2BoqwzzYBGyi1Yu1r%2B4s8oT7Y1TOn_8t_u7Xaix8ow%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
--
608.661.1184
john.pye...@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTL%3Dv%2BXo7R_Vovt5EGSPaNbRogvVK7WGeL%3DeP08Z1pyTx7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Can't get puppet/passenger to stop using /home/puppet/.puppet
I've followed all of the documentation at
http://docs.puppetlabs.com/guides/passenger.html to try to switch from
webrick to passenger/apache.
I'm obviously doing something wrong however because I can't get passenger
to use /etc/puppet instead of /home/puppet/.puppet to store data.
Any ideas would be appreciated. Below are some of the details.
I'm running it on Ubuntu 12
I'm using Apache 2.2.22
I'm using puppet 3.4.0
I'm using passenger 4.0.41
1) I've created the directories /usr/share/puppet/rack/puppetmasterd with
./public ./tmp directories
2) In that directory I've put in a config.ru that looks like this:
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not in your RUBYLIB:
# $:.unshift('/var/lib/puppet')
$0 = "master"
# if you want debugging:
# ARGV << "--debug"
ARGV << "--rack"
*ARGV << "--confdir" << "/etc/puppet"ARGV << "--vardir" <<
"/var/lib/puppet"*require 'puppet/application/master'
# we're usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Application[:master].run
3) I've created the file /etc/apache2/sites-available/passenger with the
following snippet
DocumentRoot */usr/share/puppet/rack/puppetmasterd/public*
Options None
AllowOverride None
# Apply the right behavior depending on Apache version.
Order allow,deny
Allow from all
No matter what I've tried it still puts everything to /home/puppet/.puppet
directory instead of using /etc/puppet
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
--
608.661.1184
john.pye...@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTLk4w%2BJJN5GvgBz%3DNA8%2BTTcfQ49ZCD0AABdU2E-mCBhQNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Can't get puppetmaster working with passenger
Tried to convert from webrick to passenger today. Failed. When I run puppet agent -tv I get two things that are troubling. 1) I get this message: Notice: with older puppet master. To remove this notice, please upgrade your master(s) Notice: to Puppet 3.3 or newer. Even though in my webrick days we are running puppet 3.4 on the puppetmaster. 2) I also get these messages. Warning: Local environment: "dev" doesn't match server specified node environment "production", switching agent to "production". Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class bastion for 10.0.11.83 on node My /etc/puppet/puppet.conf is configured correctly because it was working in the webbrick world. Additionally, I know it is getting some information from my puppet.conf file because it is correctly executing my ENC script defined in external_nodes= It just doesn't seem to be recognizing my extra modulepath= and manifest= values for my [dev] stanza. I've checked file/directory permissions and the apache user www-data has read permissions to those directories. Any ideas??? -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLnBypf%3DwxEP44%2Bs0Y_aSZNYpGVSEkXnJAOPYm2eWciR8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Error 4000 on SERVER: Could not find class
We are periodically seeing the error *Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class webadminserver* In our puppet agent logs even though the module/webadminserver files are there. But I'm wondering if there is a timing/file refresh issue involved. When we push new code out to our puppetmaster we perform the following steps: 1) copy the new code to a temporary location on the puppetmaster 2) rm -rf the modules directory the puppetmaster uses 3) cp -r from the temporary location into the modules directory Sometimes when the puppet agent's next run we will see the error described above. I'm wondering if the puppetmaster is not refreshing its inode values between the time of the rm/cp combination and a puppet agent's attempt to pull down the new code. Has anyone ever seen this? Does my hypothesis make sense? Does anyone have a better way to deploy the code to puppetmaster remotely without an outage? -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTL%3DNPpgU%3DrbagtmeJAv-JFXzndHULnB6G7p13Qki7BmEAw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] controlling argument passed to ENC script for AWS
I think I have this resolved. the certname was in fact the solution. I had a permissions problem that looked like things weren't working correctly. Once I got that straightened out the value passed into my ENC script (vpc-id plus hostname) worked fine. Thanks On Thu, Feb 27, 2014 at 4:19 PM, Patrick Kelso wrote: > On Fri, Feb 28, 2014 at 8:57 AM, John Pyeatt > wrote: > > I am trying to use one puppetmaster to support multiple AWS VPCs. In > other > > words, I am trying to have one puppetmaster support multiple independent > > networks. > > > > The problem with this is that it is possible for machines on two > different > > VPCs to have the same hostname/ipaddress. > > > > I use an ENC script on the puppetmaster to classify what types of > classes to > > load to an agent machine based on the hostname that is passed to the ENC > > script. > > > > But the hostname isn't enough information because as I mentioned above, > two > > different agents might have the same hostname but live in different VPCs. > > > > Is there any way to customize the identifier that is passed from the > agent > > to the enc script on the puppetmaster? Ideally, I would like to pass the > > vpc-id and the hostname. That would guarantee uniqueness. > > > > I looked at the puppet inventory service a bit, but I don't think that > would > > solve my problem either. > > John, > > Have you had a look at using the Amazon AMI metadata? Set a > customer tag for the VPC env and use it with Puppet. > > This is what I've used to solve a similar issue. > http://stackoverflow.com/a/19785580 > > Regards, > Patrick Kelso > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CANf9H4YLNVvJ0iDVKVSMojPpUQGQ5cJoFXq87%3DJ%3DP3JnrvFNgQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTL%3DTEx7CF4iAzeUYVa-yfwJ1z-YxkUKJyRR5FA7RNquAkQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] controlling argument passed to ENC script for AWS
See comments below. On Thu, Feb 27, 2014 at 4:45 PM, Christopher Wood < christopher_w...@pobox.com> wrote: > (inline) > > On Thu, Feb 27, 2014 at 03:57:21PM -0600, John Pyeatt wrote: > >I am trying to use one puppetmaster to support multiple AWS VPCs. In > other > >words, I am trying to have one puppetmaster support multiple > independent > >networks. > > > >The problem with this is that it is possible for machines on two > different > >VPCs to have the same hostname/ipaddress. > > If two machines have the same ip address, how does your puppetmaster route > to them both? > (I thought it was the agent that was initiating the connection, not the puppetmaster, so in that context the ip address of the agent doesn't matter. In the ENC processing it does). > > >I use an ENC script on the puppetmaster to classify what types of > classes > >to load to an agent machine based on the hostname that is passed to > the > >ENC script. > > This sounds like you want to use a non-hostname certname, set in the > puppet.conf on build. > > http://docs.puppetlabs.com/references/latest/configuration.html#certname > > (That's different. That's the name of the certificate as it is stored in /etc/puppet/ssl/cert/signed.) What I need to control is the value for the first, and only argument that is passed to the ENC. > >But the hostname isn't enough information because as I mentioned > above, > >two different agents might have the same hostname but live in > different > >VPCs. > > > >Is there any way to customize the identifier that is passed from the > agent > >to the enc script on the puppetmaster? Ideally, I would like to pass > the > >vpc-id and the hostname. That would guarantee uniqueness. > > > >I looked at the puppet inventory service a bit, but I don't think that > >would solve my problem either. > >-- > >John Pyeatt > >Singlewire Software, LLC > >[1]www.singlewire.com > >-- > >608.661.1184 > >[2]john.pye...@singlewire.com > > > >-- > >You received this message because you are subscribed to the Google > Groups > >"Puppet Users" group. > >To unsubscribe from this group and stop receiving emails from it, > send an > >email to puppet-users+unsubscr...@googlegroups.com. > >To view this discussion on the web visit > >[3] > https://groups.google.com/d/msgid/puppet-users/CAEisTLmNnN7AyfdxgAWvAHrgB3G9O4c_pk1eT%2BPkOh5b7%3Ddv9g%40mail.gmail.com > . > >For more options, visit [4]https://groups.google.com/groups/opt_out. > > > > References > > > >Visible links > >1. http://www.singlewire.com/ > >2. mailto:john.pye...@singlewire.com > >3. > https://groups.google.com/d/msgid/puppet-users/CAEisTLmNnN7AyfdxgAWvAHrgB3G9O4c_pk1eT%2BPkOh5b7%3Ddv9g%40mail.gmail.com > >4. https://groups.google.com/groups/opt_out > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/20140227224529.GA4547%40iniquitous.heresiarch.ca > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLmTEoO-wtSQpkQND20Dw%3DtksedaZZyCngte-d8hr%3DQSZw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] controlling argument passed to ENC script for AWS
I am trying to use one puppetmaster to support multiple AWS VPCs. In other words, I am trying to have one puppetmaster support multiple independent networks. The problem with this is that it is possible for machines on two different VPCs to have the same hostname/ipaddress. I use an ENC script on the puppetmaster to classify what types of classes to load to an agent machine based on the hostname that is passed to the ENC script. But the hostname isn't enough information because as I mentioned above, two different agents might have the same hostname but live in different VPCs. Is there any way to customize the identifier that is passed from the agent to the enc script on the puppetmaster? Ideally, I would like to pass the vpc-id and the hostname. That would guarantee uniqueness. I looked at the puppet inventory service a bit, but I don't think that would solve my problem either. -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLmNnN7AyfdxgAWvAHrgB3G9O4c_pk1eT%2BPkOh5b7%3Ddv9g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] When does puppet agent load newly installed facter facts?
I think I have run into some sort of facter caching issue in the puppet
agent that I am hoping someone can explain.
When I launch a new server I run the following command to get things
started.
puppet agent --test --onetime --no-daemonize --waitforcert 5
The puppetmaster then downloads to the server as one would expect. Included
in this download are some new custom facts (one is called
cassandra_home_dir) that I have written. It correctly puts them in
/var/lib/puppet/lib/facter.
After the puppet agent has downloaded the custom facts it continues
processing. In one of my .pp files there is a resource declaration as
follows:
file {"cassandraEnv":
owner => 'cassandra',
group => 'cassandra',
mode => '744',
ensure => present,
path => "*${cassandra_home_dir}*/conf/cassandra-env.sh",
content => template('db/cassandra-env.sh.template.erb'),
require => Exec['installCassandra'],
}
But it is failing on this resource because ${cassandra_home_dir} is empty
and therefore it is trying to put the file in the /conf directory which
doesn't exist. The Exec['installCassandra'] executed correctly immediately
prior to the attempt to create the file['cassandraEnv'] resource. So I know
the appropriate information is available from the file system.
If I run the puppet agent command again everything works fine because the
${cassandra_home_dir} variable is no longer empty. So I have done nothing
different other than rerun the puppet agent.
*Does puppet agent cache facter facts at startup that is preventing it from
loading my newly downloaded fact?*
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
--
608.661.1184
john.pye...@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTL%3D-%3DLyqHUOwNrumVr2b9jr7BrCBpapgfvT2te5PgTVu2w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet environments not working
Not certain if this is the issue or not, but there seems to be a bug in the
master regarding when the configuration file is read to override the
default settings. Try doing this:
1) start up your puppet master
2) after it is up and running try running this from the command line *touch
/etc/puppet/puppet.conf* this will force the puppet master to reparse the
configuration settings.
I had a similar problem reading modulepath=. There is apparently a fix for
this in 3.4
On Tue, Dec 17, 2013 at 7:02 AM, Chantal Rosmuller wrote:
> Hi,
>
> On our puppet server the puppet environments do not seem to work. This is
> our puppet.conf:
>
> [main]
> logdir=/var/log/puppet
> vardir=/var/lib/puppet
> ssldir=/var/lib/puppet/ssl
> rundir=/var/run/puppet
> factpath=$vardir/lib/facter
> confdir=/etc/puppet
> templatedir=$confdir/templates
> modulepath=$confdir/modules
> manifest=$confdir/manifests/site.pp
> manifestsdir=$confdir/manifests
> hiera_config=/etc/puppet/hiera.yaml
> pluginsync = true
>
> [master]
> certname= puppet3.domain.com
> hostprivkey = /var/lib/puppet/ssl/private_keys/puppet3.domain.com.pem
> {mode = 640}
> ssl_client_header = HTTP_X_CLIENT_DN
> ssl_client_verify_header = HTTP_X_CLIENT_VERIFY
> # ssl_client_header = SSL_CLIENT_S_DN
> # ssl_client_verify_header = SSL_CLIENT_VERIFY
> reports = store,tagmail
> #reports = store,tagmail,puppetdb
> storeconfigs = true
> storeconfigs_backend = puppetdb
>
> [dev]
> modulepath=$confdir/environments/dev/modules
> manifest=$confdir/environments/dev/manifests/site.pp
>
> When i try
>
> puppet agent --environment dev --no-daemonize --verbose --onetime
>
> The changes in dev are not applied. Can it have anything to do with
> puppetdb?
>
> The servers seems to recognize the puppet environment:
>
> puppet module list --environment 'dev'
>
> returns:
>
> /etc/puppet/environments/dev/modules
> ├── aliases (???)
> ├── apt (???)
> etc
>
>
> versions on the server:
>
> ii puppet 3.3.1-1puppetlabs1all
>Centralized configuration management - agent startup and
> compatibility scripts
> ii puppet-common 3.3.1-1puppetlabs1all
>Centralized configuration management
> ii puppetdb 1.5.0-1puppetlabs1all
>PuppetDB Centralized Storage.
> ii puppetdb-terminus 1.5.0-1puppetlabs1all
>Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
> ii puppetmaster 3.3.1-1puppetlabs1all
>Centralized configuration management - master startup and
> compatibility scripts
> ii puppetmaster-common3.3.1-1puppetlabs1all
>Puppet master common scripts
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/2b3130a5-1641-4f60-9bc7-88b4bfb4fff5%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
--
608.661.1184
john.pye...@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTLm%2Bb%3DfRbbR_dXBTBmFKoRRU7n0Ar6n4bAwN7sMJqJL7tw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
OK, Here is something I found with this problem When I run /etc/init.d/puppetmaster start in node/environment.rb validate_dirs is being passed /etc/puppet/modules:/usr/share/puppet/modules which isn't what I have in /etc/puppet/puppet.conf modulepath=. BUT! if I just do a *touch /etc/puppet/puppet.con*fthen puppetmaster calls reparse_config_files and it does in fact read my /etc/puppet/puppet.conf modulepath= correctly Like I said in the original thread, I don't know the ruby language. But I suspect that there is some type of calling sequence issue going on. On Thu, Dec 12, 2013 at 2:57 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > Yes. > > The agent does default to environment=production if not specified > otherwise. Your [production] should match your [main] wrt. modulepath etc. > > HTH, > Felix > > On 12/11/2013 09:59 PM, John Pyeatt wrote: > > Could it be because my puppet.conf has a [production], [test] and > > [development] environment with a modulepath= for each one? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A97A8E.2000308%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLkPc7J_ofHZU0o1psP8QOiZFwe7ggcOg3B9%3Dk3Xbs_8Ww%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
uppet (debug): file_metadata supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:28:35 + Puppet (info): Caching node for ip-10-0-22-34 *2013-12-11 20:28:35 + Puppet (warning): Host is missing hostname and/or domain: ip-10-0-22-342013-12-11 20:28:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-342013-12-11 20:28:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-342013-12-11 20:28:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34* 2013-12-11 20:28:35 + Puppet (debug): Finishing transaction 20195420 2013-12-11 20:28:35 + Puppet (debug): Received report to process from ip-10-0-22-34 2013-12-11 20:28:35 + Puppet (debug): Processing report from ip-10-0-22-34 with processor Puppet::Reports::Store 2013-12-11 20:29:03 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:29:03 + Puppet (debug): node supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:29:03 + Puppet (debug): file_metadata supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:29:05 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (warning): Host is missing hostname and/or domain: ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (debug): Received report to process from ip-10-0-22-34 2013-12-11 20:29:05 + Puppet (debug): Processing report from ip-10-0-22-34 with processor Puppet::Reports::Store 2013-12-11 20:29:33 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:29:33 + Puppet (debug): node supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:29:33 + Puppet (debug): file_metadata supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:29:35 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (warning): Host is missing hostname and/or domain: ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (debug): Received report to process from ip-10-0-22-34 2013-12-11 20:29:35 + Puppet (debug): Processing report from ip-10-0-22-34 with processor Puppet::Reports::Store 2013-12-11 20:30:03 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:30:03 + Puppet (debug): node supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:30:03 + Puppet (debug): file_metadata supports formats: pson b64_zlib_yaml yaml raw 2013-12-11 20:30:05 + Puppet (info): Caching node for ip-10-0-22-34 2013-12-11 20:30:05 + Puppet (warning): Host is missing hostname and/or domain: ip-10-0-22-34 2013-12-11 20:30:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:30:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 2013-12-11 20:30:05 + Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on node ip-10-0-22-34 On Tue, Dec 10, 2013 at 10:30 AM, John Pyeatt wrote: > OK, I'll give your suggestions a shot. I've got meeting the rest of the > day... lucky me. Thanks for all of the help. It is greatly appreciated. > > > On Tue, Dec 10, 2013 at 10:23 AM, Felix Frank < > felix.fr...@alumni.tu-berlin.de> wrote: > >> Hmm, indeed. Do run as user puppet to see if that's different. >> >> Otherwise, looks like you will need to stop the puppetmaster daemon (or >> apache if using passenger) and launch a debug version of the master with >> webrick >> >> puppet master --no-daemonize -dv >> >> Then have an agent check in and watch the master output for clues. >> >> HTH, >> Felix >> >> On 12/10/2013 05:15 PM, John Pyeatt wrote: >> > I assume you wanted me to run this on the puppetmaster correct? It looks >> > like it is being found >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/52A74015.3010108%40alumni.tu-berlin.de >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > John Pyeatt > Singlewire Software, LLC > www.singlewire.com > -- > 608.661.1184 > john.pye...@singlewire.com > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTL%3DJqKXZ9G0CguY9obUyoBhukKp3jSnGjEMGmovvsXk2hw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
OK, I'll give your suggestions a shot. I've got meeting the rest of the day... lucky me. Thanks for all of the help. It is greatly appreciated. On Tue, Dec 10, 2013 at 10:23 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > Hmm, indeed. Do run as user puppet to see if that's different. > > Otherwise, looks like you will need to stop the puppetmaster daemon (or > apache if using passenger) and launch a debug version of the master with > webrick > > puppet master --no-daemonize -dv > > Then have an agent check in and watch the master output for clues. > > HTH, > Felix > > On 12/10/2013 05:15 PM, John Pyeatt wrote: > > I assume you wanted me to run this on the puppetmaster correct? It looks > > like it is being found > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A74015.3010108%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLnzLH8FwiP4pu9ZZFMwx2-PYs2cFHZ3YD%3DGjTrq1cKZXg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
I assume you wanted me to run this on the puppetmaster correct? It looks
like it is being found
Here is the output
[root@puppetmaster modules]# puppet apply -dv -e "include ec2metadata"
Info: Loading facts in
/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/subnetid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/vpcid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/azname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/instanceid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/mac.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/vpcname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/instancetype.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/localipv4.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/regionname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/accesskey.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/ec2_instance_server_type.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/secretkey.rb
Debug: importing
'/opt/singlewire/ourrepo/modules/ec2metadata/manifests/init.pp' in
environment production
Debug: Automatically imported ec2metadata from ec2metadata into production
Debug: importing
'/opt/singlewire/ourrepo/modules/ec2metadata/manifests/init.pp' in
environment production
Debug: Automatically imported ec2metadata from ec2metadata into production
Notice: Compiled catalog for puppetmaster.pyeatt.singlewire.com in
environment production in 0.06 seconds
Debug: Creating default schedules
Debug: Failed to load library 'selinux' for feature 'selinux'
Debug: Using settings: adding file resource 'confdir':
'File[/etc/puppet]{:path=>"/etc/puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'vardir':
'File[/var/lib/puppet]{:path=>"/var/lib/puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Failed to load library 'shadow' for feature 'libshadow'
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/subnetid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/vpcid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/azname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/instanceid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/mac.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/vpcname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/instancetype.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/localipv4.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/regionname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/accesskey.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/ec2_instance_server_type.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/secretkey.rb
Debug: Loaded state in 0.01 seconds
Info: Applying configuration version '1386691733'
Debug: Finishing transaction 25450780
Debug: Storing state
Debug: Stored state in 0.01 seconds
Notice: Finished catalog run in 0.10 seconds
Debug: Using settings: adding file resource 'rrddir':
'File[/var/lib/puppet/rrd]{:path=>"/var/lib/puppet/rrd", :mode=>"750",
:owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false}'
Debug: Finishing transaction 25348500
On Tue, Dec 10, 2013 at 10:00 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> Okay, looks fine so far.
>
> Next, can you share the output of
>
> puppet apply -dv -e 'include ec2metadata'
>
> Thanks in advance!
>
> On 12/10/2013 04:37 PM, John Pyeatt wrote:
> > Full puppet.conf
> >
> > [main]
> > pluginsync = true
> > vardir = /var/lib/puppet
> > logdir = /var/log/puppet
> > rundir = /var/run/puppet
> > modulepath = /etc/puppet/modules:/opt/ourrepo/puppetmaster/modules
> > ssldir = $vardir/ssl
> >
> > Full path to the ec2metadata manifest is
> > /opt/ourre
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
Full puppet.conf [main] pluginsync = true vardir = /var/lib/puppet logdir = /var/log/puppet rundir = /var/run/puppet modulepath = /etc/puppet/modules:/opt/ourrepo/puppetmaster/modules ssldir = $vardir/ssl Full path to the ec2metadata manifest is /opt/ourrepo/puppetmaster/modules/ec2metadata/manifests/init.pp On Tue, Dec 10, 2013 at 9:14 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 12/10/2013 04:08 PM, John Pyeatt wrote: > > My puppetmaster is running as the user puppet. I logged into the system > > as puppet and was able to access the directory > > /opt/our-repo/puppetmaster/modules. I did a chown -R puppet:puppet > > /opt/our-repo/puppetmaster just to make certain and it still is > > unrecognised. Just get the message in the puppet client log. > > > > 2013-12-10 14:57:51 + Puppet (err): Could not retrieve catalog from > > remote server: Error 400 on SERVER: Could not find class ec2metadata for > > ip-10-0-22-220 on node ip-10-0-22-220 > > OK, so what's the full path to the manifest file that defines the class > ec2metadata? Can you share your full puppet.conf? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A72FD0.3060208%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLm2hzNLLQ5bwQ226OUiejQoN3%3Dc8LD%3DCCJ9HxKhwotm7g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
My puppetmaster is running as the user puppet. I logged into the system as puppet and was able to access the directory /opt/our-repo/puppetmaster/modules. I did a chown -R puppet:puppet /opt/our-repo/puppetmaster just to make certain and it still is unrecognised. Just get the message in the puppet client log. 2013-12-10 14:57:51 + Puppet (err): Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class ec2metadata for ip-10-0-22-220 on node ip-10-0-22-220 On Tue, Dec 10, 2013 at 7:02 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > Hi, > > the approach looks fine. Can you share the complete path to the newapp > class when it's not working? > > Beware that the puppet master process drops its privileges after basic > initialization. You may have to make sure that the puppet user (or > whichever is being used) can access your alternate modules tree. > > HTH, > Felix > > On 12/06/2013 08:12 PM, john.pye...@singlewire.com wrote: > > > > _Can anyone tell me the incantation I need to make puppetmasterd > > recognize my /opt/our-repo/puppetmaster/modules directory_? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A710DB.2060500%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. > -- John Pyeatt Singlewire Software, LLC www.singlewire.com -- 608.661.1184 john.pye...@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLmkA4z15bgKC3TpdmDzwCqrLGDJPPH8QdfikjofKSOrWw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Can't seem to get modulepath attribute recognized by puppetmasterd
Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet master --configprint modulepath and I in fact see /etc/puppet/modules:/opt/our-repo/puppetmaster/modules But when I restart puppetmasterd I get the following errors. 2013-12-06 19:05:09 + Puppet (err): Could not find class newapp for ip-10-0-22-5 on node ip-10-0-22-5 On the clients I get the message Puppet (err): Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class newapp for ip-10-0-22-5 on node ip-10-0-22-5 If I move my newapp module to /etc/puppet/modules it works fine. So I think the module itself isn't the problem. I've also tried moving the modulepath= to the [master] stanza but things still don't work. *Can anyone tell me the incantation I need to make puppetmasterd recognize my /opt/our-repo/puppetmaster/modules directory*? Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f59f9ac3-ff1b-4411-92a4-59aacb685522%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
