[Puppet Users] v3 agent to v4 master ssl issue

[Christopher Wood]

I have a puppet 3 agent attempting an agent run against a puppet 4 master but I 
am getting ssl errors. I'm out of google-fu and I've verified certs and keys, 
run both sides in debug using puppetserver and the rack "puppet master 
--no-daemonize --verbose", and am not seeing anything that jumps out at me. I 
do notice that when running in DEBUG the puppetserver log doesn't spit output 
during the agent run.

The closest I can get to understanding this is stackoverflow, but I'm not sure 
how I would tell the agent to use TLSv1.2.

http://stackoverflow.com/questions/25814210/opensslsslsslerror-ssl-connect-syscall-returned-5-errno-0-state-sslv3-read

Any hints on what these ssl errors are from and how I can fix this?

SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A

[root@mail10c2 ~]# puppet --version
3.8.5
[root@mail10c2 ~]# cat /etc/redhat-release
CentOS release 6.7 (Final)
[root@mail10c2 ~]# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013

[root@puppetmaster1stage ~]# rpm -q puppetserver
puppetserver-2.2.1-1.el6.noarch
[root@puppetmaster1stage ~]# /opt/puppetlabs/bin/puppet --version
4.3.2
[root@puppetmaster1stage ~]# cat /etc/redhat-release
CentOS release 6.7 (Final)
[root@puppetmaster1stage ~]# /opt/puppetlabs/puppet/bin/openssl version
OpenSSL 1.0.2e 3 Dec 2015

I've verified the hostcert, hostpubkey, and localcacert as definitely belonging 
to each other using openssl. These files exist at the paths from "puppet config 
print". The localcacert is definitely the CA cert that both server and client 
use, by md5sum.

This is the output (that is definitely the --server in the server cert):

[root@mail10c2 util]# puppet agent --onetime --verbose --no-daemonize 
--no-splay --server puppetmaster1stage
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources 
using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read 
finished A
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve 
file metadata for puppet://puppetmaster1stage/pluginfacts: SSL_connect SYSCALL 
returned=5 errno=0 state=SSLv3 read finished A
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read 
finished A
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file 
metadata for puppet://puppetmaster1stage/plugins: SSL_connect SYSCALL 
returned=5 errno=0 state=SSLv3 read finished A
Info: Loading facts
Error: Could not retrieve catalog from remote server: SSL_connect SYSCALL 
returned=5 errno=0 state=SSLv3 read finished A
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: SSL_connect SYSCALL returned=5 errno=0 
state=SSLv3 read finished A

-- 
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/20160205215603.GA24864%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] bizarro error when starting a puppet agent

[Peter Berghold]

First a disclaimer:   I am trying to provide support for our production
team setting up a system as a Puppet agent node and most of the work I'm
doing is being handled with the operations team acting as my voice operated
keyboards.


I handed my operations team instructions on how to install a Puppet client
on some of our production boxes.  One such box when running the agent for
the first time issues the following error and the run fails:

"Error: Could not run command from postrun_command: Execution of
'/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not execute
posix command: No such file or directory -
/etc/puppet/etckeeper-commit-post"

Never saw this error before and I'm quite baffled by it.  Where is this
coming from and what is Puppet trying to tell me?


Thanks in advance.

-- 
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/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Creating module structure with Foreman that removes settings when a module no longer applies (like GPOs)

[jmp242]

I'm thinking about this, and it may be a total waste of time, but 
occasionally we want to change the configuration of an existing computer. 
We could totally re-image the computers, but that seems like it might be a 
big time sink compared to resetting when the hostgroup changes. It also 
seems like a good way to make sure you know what configuration is applied 
if a computer is moved across hostgroups.

My current best idea for this is to use an inheritance method, but 
Inheritance is discouraged. However, it seems like it would be quite clean:

Each module would have:
module
module::applied

The module would actually have the steps to back out whatever 
module::applied did. module would be applied at the top hostgroup, and then 
in the hostgroup or systemgroup that is set up for a particular 
configuration the module::applied would override or do the actual 
configuration...

Is this a totally crazy idea? Or will it work like I'm thinking, and also 
work with 4.x?

-- 
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/577d0b78-b25f-42ab-b609-64a624276598%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Can puppet send email specific to a host?

[Ken Barber]

Perhaps you might want to modify the tagmail reporter, to handle this
yourself. A report handler gets passed the environment, so it
shouldn't be possible to massage it into shape. FWIW, tagmail has been
removed from the latest source of Puppet, full explanation here:
https://tickets.puppetlabs.com/browse/PUP-3463

ken.

On Mon, Feb 1, 2016 at 11:08 PM,   wrote:
> Please let me know if Puppet has a feature which can send emails specific to
> an environment?
> The tagmail feature sends emails of all the agents communicating to the
> master and that is not what we want in our implementation.
>
> Please advise.
>
> --
> 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/20f7b179-8f88-422c-85ad-87ceaaa2e16b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/CAE4bNTmdToaA9Arh-kBiN9HGkgULzRqD6h6DUSu%2B_LhJtP0S9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Creating module structure with Foreman that removes settings when a module no longer applies (like GPOs)

[Garrett Honeycutt]

On 2/5/16 12:33 PM, jmp242 wrote:
> I'm thinking about this, and it may be a total waste of time, but
> occasionally we want to change the configuration of an existing
> computer. We could totally re-image the computers, but that seems like
> it might be a big time sink compared to resetting when the hostgroup
> changes. It also seems like a good way to make sure you know what
> configuration is applied if a computer is moved across hostgroups.
> 
> My current best idea for this is to use an inheritance method, but
> Inheritance is discouraged. However, it seems like it would be quite clean:
> 
> Each module would have:
> module
> module::applied
> 
> The module would actually have the steps to back out whatever
> module::applied did. module would be applied at the top hostgroup, and
> then in the hostgroup or systemgroup that is set up for a particular
> configuration the module::applied would override or do the actual
> configuration...
> 
> Is this a totally crazy idea? Or will it work like I'm thinking, and
> also work with 4.x?
> 

Hi jmp242,

I'm leaning toward totally crazy :)

Your system provisioning process should provisional a minimal system and
then configure and manage it with Puppet. If your goal is to reuse that
system, then just re-provision it. This will ensure you are not dragging
around cruft that then becomes depended on.

For example, you build role A, then change system to role B and
everything works but when you build role B from scratch it fails because
it was depending on something from role A that was not described by role B.

WRT rebuilding being a time sink, I normally see bare metal to fully
puppetized systems using PXE taking around 15 minutes if you have local
copies of your repos. Potentially much shorter times if you are using VM
images, containers, jails, etc.

Best regards,
-g

-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
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/56B4EA01.1080606%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] bizarro error when starting a puppet agent

[Matthaus Owens]

Peter,

To allow us to be more helpful, it would be great if you could include
which version of puppet you are installing and from where. From the problem
you describe, I imagine you are installing from debian or ubuntu.

They include 2 files in their package /etc/puppet/etckeeper-commit-pre
and /etc/puppet/etckeeper-commit-post that are referenced in the
puppet.conf that ships with the package. It looks like etckeeper is
designed to allow someone to version control the etc directory (
https://joeyh.name/code/etckeeper/). The error you're seeing indicates that
the file doesn't exist, so there are 2 options to resolve it.

1. Edit /etc/puppet/puppet.conf to remove or disable the prerun_command and
postrun_command settings.
2. Reinstall the package to try to get the etckeeper-commit-post file back
(this assumes you are using the debian/ubuntu puppet packages)

Another option would be to use the Puppet Labs' apt repositories instead of
debian/ubuntu. We don't ship with those settings on by default in our
packages.

HTH

On Fri, Feb 5, 2016 at 8:18 AM, Peter Berghold 
wrote:

> First a disclaimer:   I am trying to provide support for our production
> team setting up a system as a Puppet agent node and most of the work I'm
> doing is being handled with the operations team acting as my voice operated
> keyboards.
>
>
> I handed my operations team instructions on how to install a Puppet client
> on some of our production boxes.  One such box when running the agent for
> the first time issues the following error and the run fails:
>
> "Error: Could not run command from postrun_command: Execution of
> '/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not execute
> posix command: No such file or directory -
> /etc/puppet/etckeeper-commit-post"
>
> Never saw this error before and I'm quite baffled by it.  Where is this
> coming from and what is Puppet trying to tell me?
>
>
> Thanks in advance.
>
> --
> 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/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Matthaus Owens
Puppet Labs

-- 
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/CACD%3DwAekA%2BxkVk-doG3LAsaR%3D1moR2VMd-vk2oLYvU0kEtcJLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] bizarro error when starting a puppet agent

[Christopher Wood]

It may be useful to provide them with a puppet manifest which configures most 
of the puppet agent. If all they need to do is "yum install puppet; puppet 
apply file.pp" that might simplify things from both ends.

On Fri, Feb 05, 2016 at 10:00:14PM +, Peter Berghold wrote:
>Just the questions you asked prompted me to ask my operators more
>questions.   Seems instructions were not followed when they configured
>Puppet so a quick correction solved the problem.  Thanks. 
>On Fri, Feb 5, 2016 at 3:54 PM Peter Berghold <[1]salty.cowd...@gmail.com>
>wrote:
> 
>  Puppet version: 3.7.2
>  OS Family:  RHEL
>  lsbdistdescription => Red Hat Enterprise Linux Server release 6.5
>  (Santiago)
>  On Fri, Feb 5, 2016 at 2:10 PM Matthaus Owens
>  <[2]matth...@puppetlabs.com> wrote:
> 
>Peter,
>To allow us to be more helpful, it would be great if you could include
>which version of puppet you are installing and from where. From the
>problem you describe, I imagine you are installing from debian or
>ubuntu.
>They include 2 files in their package /etc/puppet/etckeeper-commit-pre
>and /etc/puppet/etckeeper-commit-post that are referenced in the
>puppet.conf that ships with the package. It looks like etckeeper is
>designed to allow someone to version control the etc directory
>([3]https://joeyh.name/code/etckeeper/). The error you're seeing
>indicates that the file doesn't exist, so there are 2 options to
>resolve it.
>1. Edit /etc/puppet/puppet.conf to remove or disable the
>prerun_command and postrun_command settings.
>2. Reinstall the package to try to get the etckeeper-commit-post file
>back (this assumes you are using the debian/ubuntu puppet packages)
>Another option would be to use the Puppet Labs' apt repositories
>instead of debian/ubuntu. We don't ship with those settings on by
>default in our packages.
>HTH
>On Fri, Feb 5, 2016 at 8:18 AM, Peter Berghold
><[4]salty.cowd...@gmail.com> wrote:
> 
>  First a disclaimer:   I am trying to provide support for our
>  production team setting up a system as a Puppet agent node and most
>  of the work I'm doing is being handled with the operations team
>  acting as my voice operated keyboards.   
>  I handed my operations team instructions on how to install a Puppet
>  client on some of our production boxes.  One such box when running
>  the agent for the first time issues the following error and the run
>  fails:
>  "Error: Could not run command from postrun_command: Execution of
>  '/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not
>  execute posix command: No such file or directory -
>  /etc/puppet/etckeeper-commit-post"
>  Never saw this error before and I'm quite baffled by it.  Where is
>  this coming from and what is Puppet trying to tell me?
>  Thanks in advance.
> 
>  --
>  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 [5]puppet-users+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
>  
> [6]https://groups.google.com/d/msgid/puppet-users/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com.
>  For more options, visit [7]https://groups.google.com/d/optout.
> 
>--
>Matthaus Owens
>Puppet Labs
> 
>--
>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 [8]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [9]https://groups.google.com/d/msgid/puppet-users/CACD%3DwAekA%2BxkVk-doG3LAsaR%3D1moR2VMd-vk2oLYvU0kEtcJLg%40mail.gmail.com.
>For more options, visit [10]https://groups.google.com/d/optout.
> 
>--
>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 [11]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [12]https://groups.google.com/d/msgid/puppet-users/CAArvnv2ajxgCAC%3DxR9ach0NDLBZhhz3vMqNFP6pfL-7yXJkZwg%40mail.gmail.com.
>For more options, visit [13]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:salty.cowd...@gmail.com
>2. mailto:matth...@puppetlabs.com
>3. https://joeyh.name/code/etckeeper/
>4. mailto:salty.cowd...@gmail.com
>5. 

Re: [Puppet Users] bizarro error when starting a puppet agent

[Peter Berghold]

Just the questions you asked prompted me to ask my operators more
questions.   Seems instructions were not followed when they configured
Puppet so a quick correction solved the problem.  Thanks.

On Fri, Feb 5, 2016 at 3:54 PM Peter Berghold 
wrote:

> Puppet version: 3.7.2
> OS Family:  RHEL
> lsbdistdescription => Red Hat Enterprise Linux Server release 6.5
> (Santiago)
>
>
> On Fri, Feb 5, 2016 at 2:10 PM Matthaus Owens 
> wrote:
>
>> Peter,
>>
>> To allow us to be more helpful, it would be great if you could include
>> which version of puppet you are installing and from where. From the problem
>> you describe, I imagine you are installing from debian or ubuntu.
>>
>> They include 2 files in their package /etc/puppet/etckeeper-commit-pre
>> and /etc/puppet/etckeeper-commit-post that are referenced in the
>> puppet.conf that ships with the package. It looks like etckeeper is
>> designed to allow someone to version control the etc directory (
>> https://joeyh.name/code/etckeeper/). The error you're seeing indicates
>> that the file doesn't exist, so there are 2 options to resolve it.
>>
>> 1. Edit /etc/puppet/puppet.conf to remove or disable the prerun_command
>> and postrun_command settings.
>> 2. Reinstall the package to try to get the etckeeper-commit-post file
>> back (this assumes you are using the debian/ubuntu puppet packages)
>>
>> Another option would be to use the Puppet Labs' apt repositories instead
>> of debian/ubuntu. We don't ship with those settings on by default in our
>> packages.
>>
>> HTH
>>
>> On Fri, Feb 5, 2016 at 8:18 AM, Peter Berghold 
>> wrote:
>>
>>> First a disclaimer:   I am trying to provide support for our production
>>> team setting up a system as a Puppet agent node and most of the work I'm
>>> doing is being handled with the operations team acting as my voice operated
>>> keyboards.
>>>
>>>
>>> I handed my operations team instructions on how to install a Puppet
>>> client on some of our production boxes.  One such box when running the
>>> agent for the first time issues the following error and the run fails:
>>>
>>> "Error: Could not run command from postrun_command: Execution of
>>> '/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not execute
>>> posix command: No such file or directory -
>>> /etc/puppet/etckeeper-commit-post"
>>>
>>> Never saw this error before and I'm quite baffled by it.  Where is this
>>> coming from and what is Puppet trying to tell me?
>>>
>>>
>>> Thanks in advance.
>>>
>>> --
>>> 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/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Matthaus Owens
>> Puppet Labs
>>
>> --
>> 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/CACD%3DwAekA%2BxkVk-doG3LAsaR%3D1moR2VMd-vk2oLYvU0kEtcJLg%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/CAArvnv2ajxgCAC%3DxR9ach0NDLBZhhz3vMqNFP6pfL-7yXJkZwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] bizarro error when starting a puppet agent

[Peter Berghold]

Puppet version: 3.7.2
OS Family:  RHEL
lsbdistdescription => Red Hat Enterprise Linux Server release 6.5 (Santiago)


On Fri, Feb 5, 2016 at 2:10 PM Matthaus Owens 
wrote:

> Peter,
>
> To allow us to be more helpful, it would be great if you could include
> which version of puppet you are installing and from where. From the problem
> you describe, I imagine you are installing from debian or ubuntu.
>
> They include 2 files in their package /etc/puppet/etckeeper-commit-pre
> and /etc/puppet/etckeeper-commit-post that are referenced in the
> puppet.conf that ships with the package. It looks like etckeeper is
> designed to allow someone to version control the etc directory (
> https://joeyh.name/code/etckeeper/). The error you're seeing indicates
> that the file doesn't exist, so there are 2 options to resolve it.
>
> 1. Edit /etc/puppet/puppet.conf to remove or disable the prerun_command
> and postrun_command settings.
> 2. Reinstall the package to try to get the etckeeper-commit-post file back
> (this assumes you are using the debian/ubuntu puppet packages)
>
> Another option would be to use the Puppet Labs' apt repositories instead
> of debian/ubuntu. We don't ship with those settings on by default in our
> packages.
>
> HTH
>
> On Fri, Feb 5, 2016 at 8:18 AM, Peter Berghold 
> wrote:
>
>> First a disclaimer:   I am trying to provide support for our production
>> team setting up a system as a Puppet agent node and most of the work I'm
>> doing is being handled with the operations team acting as my voice operated
>> keyboards.
>>
>>
>> I handed my operations team instructions on how to install a Puppet
>> client on some of our production boxes.  One such box when running the
>> agent for the first time issues the following error and the run fails:
>>
>> "Error: Could not run command from postrun_command: Execution of
>> '/etc/puppet/etckeeper-commit-post' retur ned 1: Error: Could not execute
>> posix command: No such file or directory -
>> /etc/puppet/etckeeper-commit-post"
>>
>> Never saw this error before and I'm quite baffled by it.  Where is this
>> coming from and what is Puppet trying to tell me?
>>
>>
>> Thanks in advance.
>>
>> --
>> 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/CAArvnv2zJrNqO_W3wgeAjWiFmJ%3D%2BJzyohg_is4SQ1_SU153%2BoA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Matthaus Owens
> Puppet Labs
>
> --
> 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/CACD%3DwAekA%2BxkVk-doG3LAsaR%3D1moR2VMd-vk2oLYvU0kEtcJLg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAArvnv2jYD4WrNXpt_kpJfS44bm-C7SE9%2Bee5e1MfSnksofT6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.