[Puppet Users] Re: Clean Puppet 3 to Puppet 4 migration

[Peter Souter]

One of the useful tools for an upgrade situation is the Catalog Preview 
tool. It requires Puppet 3.8, which should be a much smaller jump for you 
(3.7 -> 3.8) to begin with. It'll probably help soothe worries for the ops 
team by allowing a level of testing and certainty before the big jump.

It's pretty rad, because it will compile catalogs in the Puppet 3 format, 
and compare them with catalogs compiled with "future parser" turned on, 
which was the Puppet 4 compatibility mode avaliable for Puppet 3 for 
helping to upgrade.

Setup steps are here: https://forge.puppet.com/puppetlabs/catalog_preview

Another tool that's used is Githubs Octocatalog-diff
 https://github.com/github/octocatalog-diff 
, which is similar to 
catalog-preview

**I generally recommend a cutover to a completely new 
infra, rather than trying to upgrade in place. This is more philosophical 
than technical, as it's probably easier if you have the server resources to 
create a new shiny Puppet 4 infra, then slowly just point old servers to 
the new shiny servers in batches, picking the easiest or least breaking 
servers first (eg. lab, dev, canary servers for testing) rather than trying 
to big-bang upgrade everything at once and worrying about rollback. But I 
know this can be a harder battle with change windows and getting everyone 
aligned.**

In terms of automation, the new Bolt tool would be perfect for you here, as 
you can use bolt to run the commands needed to move servers to the new 
infra. 

We have a bootstrap task 
 avaliable, but right 
now it's PE only (it uses a particular script we host to bootstrap Puppet, 
open-source support is coming in the future) but it wouldn't be too hard to 
just use bolt to either run a script (Such as my
 https://github.com/petems/puppet-install-shell 
) or write your own 
organisational specific task to do the steps you need, and rollback if 
something goes wrong.

I'd also recommend the following talks and blogposts about Puppet 3->4 
upgrades:

   - Rob Nelsons talk about AT&T's upgrade from PuppetConf 2016 (
   https://www.youtube.com/watch?v=FWnj0xQOZN8)
   - Nacho Barrientos talk about CERN's Puppet 4 update (
   
https://puppetconf17.sched.com/event/B4wI/a-not-so-bumpy-road-to-puppet4-at-cern-nacho-barrientos-cern
 Vids 
   not out yet, soon!)
   - Skroutz's blogpost about their upgrade (
   https://engineering.skroutz.gr//blog/upgrading-puppet3-to-puppet4/
   - Githubs blogpost about their Puppet 4 Upgrade: 
   https://puppet.com/blog/upgrading-to-puppet-4-at-github
   
There's also the #upgraders room on the Puppet Slack channel if you have 
other questions :) Feel free to ping me there with questions, if I'm around 
I might be able to help (@petems)

On Wednesday, October 11, 2017 at 9:15:02 PM UTC+1, Michael Watters wrote:
>
> Been through a similar upgrade myself.  The first step would be to spin up 
> a new puppet master running Puppet Server.  You can copy over the SSL dir 
> from your old/current master to avoid SSL errors on the agents.  For 
> testing you'll want to make sure your manifests work correctly using the 
> future parser, that can be enabled in the puppet.conf file on the agents.  
> Setting up a separate environment for testing is also recommended.
>
> Puppet Server will work with 3.7 clients so once you have a manifest that 
> compiles correctly you can just point the agents to the new master's IP.
>
>
> On Wednesday, October 11, 2017 at 8:07:13 AM UTC-7, Salty Old Cowdawg 
> wrote:
>>
>> About three years ago (4 years ago?) I deployed a Puppet infrastructure 
>> for my company and department based on FOSS Puppet 3.7.   Given that's been 
>> deprecated of course I'm very much looking to migrate to Puppet 4.   
>> Besides for about three months I worked for another company and got spoiled 
>> by Puppet 4. 
>>
>> So I'm back at my old digs and assessing what it will take to go from P3 
>> to P4.   Here are some of the things I have to think about
>>
>> 1) the migration needs to be fully automated both on the server end and 
>> the client end. 
>> 2) no really this is going to be done by operations personnel who 
>> have a low threshold of fright for Puppet in spite of my best efforts to 
>> desensitize them.
>> 3) There is as penetrable firewall between me (developer) and the Puppet 
>> infrastructure servers and clients so I cannot personally intervene
>>
>> Anybody out there been through this pain and have any suggestions and 
>> pointers on how to make this happen with minimal "breakage?" 
>>
>

-- 
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/d20e2bab

[Puppet Users] Re: SSL_read:: shutdown while in init error

[Peter Souter]

Hi folks, I saw Vishal's question over on StackOverflow 
,
 
and googling it came back to here!

I answered Vishal over on SO, but thought I'd post it here for Maxim also 
and close the loop:

It seems like there was a breaking change brought in when updating the 
OpenSSL package with older Puppet 3. Puppet 3 itself is EOL since December 
of 2016, so I recommend you update to Puppet 4 or even 5, which came out 
this year.

Another benefit: Puppet 4 and onward bundles it's own openssl, so you don't 
have to worry about breaking Puppet when upgrading openssl (See puppet-agent: 
What is it, and what's in it? 
)

You can do so with my helper script:

wget -O - 
https://raw.githubusercontent.com/petems/puppet-install-shell/master/install_puppet_agent.sh
 | sudo sh

Or manually:

Puppet 5

rpm -ivh http://yum.puppetlabs.com/puppet5/puppet5-release-el-6.noarch.rpm
yum install puppet-agent -y

Puppet 4

rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-pc1-el-6.noarch.rpm
yum install puppet-agent -y


On Thursday, October 12, 2017 at 3:39:54 PM UTC+1, Vishal Bhalla wrote:
>
> Yup - we are seeing similar problems.
>
> After our client Amazon Linux boxes updated to latest OpenSSL (SL 
> 1.0.2k-fips  26 Jan 2017) we now see 
>
> Error: SSL_read:: shutdown while in init
>
> On puppet runs. Only way we could work around it was to perform a yum 
> rollback :(
>
> On Monday, 9 October 2017 12:48:09 UTC+1, Maxim Nikolaev wrote:
>>
>> Hi
>>
>> I'm using puppet agent 3.8.7 with puppetserver 2.8. Everything worked 
>> fine for long period.
>> This week we set update on openssl (version 
>> openssl-1.0.2k-7.103.amzn1.x86_6).
>> After that we started to get errors on puppet run:
>>
>>
>>
>>
>>
>> *Error: Could not set 'file' on ensure: SSL_read:: shutdown while in 
>> initError: Could not retrieve catalog from remote server: SSL_read:: 
>> shutdown while in init*I tried to play with pupptserver and puppet agent 
>> config.
>>
>> Added http_keepaalive_timout and set larger body-max-size. 
>>
>> This resolve issue on existing servers. But each time I run puppet first 
>> time - I see this again.
>> For ex, when I try to create Packer image - it always fail, because of this 
>> errors.
>>
>> I've looked for similar errors, but find nothing.
>>
>> Have someone experienced same problem?
>>
>> Thanks.
>>
>>
> --
>
> *This email was sent by a company owned by Financial Times Group Limited 
> ("FT Group "), 
> registered office at Number One Southwark Bridge, London SE1 9HL.  
> Registered in England and Wales with company number 879531. This e-mail may 
> contain confidential information. If you are not the intended recipient, 
> please notify the sender immediately, delete all copies and do not 
> distribute it further.  It could also contain personal views which are not 
> necessarily those of the FT Group.  We may monitor outgoing or 
> incoming emails as permitted by law.*
>

-- 
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/d90b922a-56d4-4d55-95fd-e44eb8ea8201%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Is ensure_resource() evil?

[Rob Nelson]

It’s not wrong, but it’s order dependent. Assuming the two or more resource
definitions have some variance, you cannot guarantee the resource will be
realized as you intend. This you have to be very careful to not have
conflicting definitions that could flip flop over time or outright
conflict.

On Wed, Oct 18, 2017 at 7:38 PM Johan Fleury  wrote:

> Le 17/10/2017 à 08:59, jcbollinger a écrit :
> > Nothing has changed with `ensure_resource()`.  The problem is not its
> > implementation details, but rather the nature of the usage modes the
> > function is *designed* to support.  The whole idea of it is flawed.  We
> can
> > reprise that discussion if you like, but you already have this very
> thread
> > and others to which it links from which you can review some of the
> > discussions that we have had before.
> >
>
> What is the problem with ensure_resource?
>
> I use it every time I have to write something like:
>
> ```
> if !defined(Foo['bar']) {
>   foo { 'bar': }
> }
> ```
>
> Am I doing it wrong?
>
> --
> Johan Fleury
> PGP Key ID : 0x5D404386805E56E6
>
> --
> 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/e7ecdc15-49bc-b6a6-ed64-795c71cca811%40arcaik.net
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Rob Nelson

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

Re: [Puppet Users] Re: Is ensure_resource() evil?

[Johan Fleury]

Le 17/10/2017 à 08:59, jcbollinger a écrit :
> Nothing has changed with `ensure_resource()`.  The problem is not its 
> implementation details, but rather the nature of the usage modes the 
> function is *designed* to support.  The whole idea of it is flawed.  We can 
> reprise that discussion if you like, but you already have this very thread 
> and others to which it links from which you can review some of the 
> discussions that we have had before.
> 

What is the problem with ensure_resource?

I use it every time I have to write something like:

```
if !defined(Foo['bar']) {
  foo { 'bar': }
}
```

Am I doing it wrong?

-- 
Johan Fleury
PGP Key ID : 0x5D404386805E56E6

-- 
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/e7ecdc15-49bc-b6a6-ed64-795c71cca811%40arcaik.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Peter Meier]

> There still a leak on Trocla database connections (latest
> gem/module/hiera backend).
> 
> I've installed a puppetserver, with only a node connected on; after 5
> days, there is 240 opened connections.

So, as you were changing a lot (new gem, module and switching to new
backend) I'm not sure whether you are still the facing exactly the same
issue as at the beginning, but just a different variant of it.

But so let's focus on the current situation as it is the one with
everything up-to-date.

I dumped the situation and my current guess on what is going wrong in
the module's issue tracker:

https://github.com/duritong/puppet-trocla/issues/25

As you have a single node in on environment that reproduces the problem
I would be happy if you could provide in the ticket more information,
specifically regarding to:

* How does your hiera config look like atm., so how is the trocla
backend hooked into the hierarchies
* How many classes does the node include during compilation
* How many class parameters are triggering the trocla backend?
* is the amount of connections growing over time, even if you don't
change anything (no new puppet code or something like that).

Estimated numbers are fine, but they should get an indication whether we
have too many caches that all keep connections open, while the actual
idea was to use the caches to not open too many connections.

thanks and best

~pete

-- 
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/cff3445a-3c2e-c115-3a14-1d5ec51e3a30%40immerda.ch.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] Re: Creating a PowerShell based fact to get Drive Letters and Labels

[Jason McMahan]

We use the windows disk facts module 
at https://forge.puppet.com/dylanratcliffe/windows_disk_facts

That should give you what you want then you can use it within your 
manifests.

On Tuesday, October 17, 2017 at 4:22:20 PM UTC-5, Ryan Murphy wrote:
>
> So I have the following powershell command that gives me the data I want, 
> but I'm not sure how I can get Puppet to ingest it as a fact.
>
> Get-WMIObject Win32_Volume | Where-Object {$_.DriveType -eq "3" -and 
> $_.Label -ne "System Reserved" } | select Name, Label 
>
> The Output looks like this.
> Name  
> Label
>   
> -
> E:\  
>  EVol 
> D:\  
>  DVol 
> C:\
>
> I wanted to get the Drive letters and labels in to a single fact in Puppet 
> so that I could build Nagios disk checks off of them, But I'm not sure how 
> to get the output to a format that Puppet will like.
>
> Any powershell / puppet fact outputs out there able to help?
>

-- 
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/89e7a419-4f86-44b2-8d9a-728c5649af84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Autofs suggestions

[Jason McMahan]

Hello,
We are looking to remove our auto mounts from ldap and manage in puppet.
We have the puppet/autofs module.

One thing we would like to do is break auto mounts from all to specific.
For instance we do not want all servers to get oracle auto mounts however 
they are in the same map file.

direct:
  mount: '/-'
  mapfile: '/etc/auto.direct'
  mapcontents:
- '/oracledb 
-fstype=nfs,vers=3,proto=tcp,timeo=600,wsize=32768,rsize=32768 
filer:/orarcledb01/stuff'
-  '/data 
-fstype=nfs,vers=3,proto=tcp,timeo=600,wsize=32768,rsize=32768 
filer:/common/data01' 

Everyone should get /data but only oracle nodes should get /data and 
/oracledb.

We have tossed ideas to try Hiera, considered concatenating files or 
strings together and placing into a auto.direct file.

Any help or suggestions is greatly appreciated.

Thank you

-- 
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/ae3ba795-59f3-4bcf-8a4d-22a35d4dc116%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Moving a node from an environment to new one causes error

[Subhi Andrews]

We are windows environment. 

Moved a couple of nodes were moved from our existing environment named tlc 
to citrix:

Here's our master puppet.conf:
rundir = /var/run/puppet

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl

environment = development

[master]
#Puppet DNS hostname
dns_alt_names = puppetdev, puppetmaster, puppetdev.parallaxfund.com, 
puppetdev.parallaxfund.com
report = true
tagmap = /etc/puppet/tagmail.conf
reports = puppetdb,console,tagmail
pluginsync = true

[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion.  Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt

# Where puppetd caches the local configuration.  An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
report = true
pluginsync =true

[citrix]
manifest = /etc/puppet/citrix/manifests/site.pp
[tlc]
manifest = /etc/puppet/tlc/manifests/site.pp
[test]
manifest = /etc/puppet/test/manifests/site.pp
#modulepath = /etc/puppet/test/modules
[production]
manifest = /etc/puppet/production/manifests/site.pp
modulepath = /etc/puppet/production/modules
[ds]
manifest = /etc/puppet/ds/manifests/site.pp

===
agent puppet.conf:
[main]
server=pfny5pptdev02
pluginsync=true
autoflush=true
environment=development

[agent]
environment=citrix
runinterval=300



If we remove citrix environment from master puppet.conf file and add the  
nodes back to tlc environment it still works.

Here's the error we see when we run the agent in test option:
PS C:\Users\sandrews> puppet agent --test --environment=citrix
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Could not find default node or by name with '
pfny5ctx03.parallaxfund.com, pfny5ctx03.parallaxfund, pfny5ctx03, 
PFNY5CTX03.parallaxfund.com, PFNY5CTX03.parallaxfund,
PFNY5CTX03' on node pfny5ctx03.parallaxfund.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
==

>From puppetserver-access.log, citrix environment


10.40.50.103 - - [18/Oct/2017:09:20:39 -0700] "POST 
/citrix/catalog/pfny5ctx03.parallaxfund.com HTTP/1.1" 400 212 "-" "Ruby" 73
10.40.50.103 - - [18/Oct/2017:09:20:39 -0700] "GET 
/tlc/file_metadatas/pluginfacts?links=manage&recurse=true&ignore=.svn&ignore=CVS&ignore=.git&checksum_type=md5
 
HTTP/1.1" 200 278 "-" "Ruby" 17


Our puppet version is 3.8.7. Anyone has any clues on how to solve this?


Thanks a lot,

Subhi.

-- 
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/80018729-b87f-4d53-a91d-b9ea184d4ba1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Terraform module available to deploy Puppet to a Nomad cluster.

[Bill Ward]

I wrote a Terraform module to deploy a puppet server environment to a Nomad 
cluster.  https://registry.terraform.io/modules/admintome/puppet/nomad/0.1.0  

I also wrote an article on my blog on how to use 
it: http://www.admintome.com/blog/terraform-module-for-puppet-in-docker/

This let's you stand up a puppet server environment with Puppet Server, 
PuppetDB, Postrgres and r10k with only a couple commands.  

-- 
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/96e58fbf-7d49-41e2-8209-d8c3792d5970%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Poil]

The Trocla leak seems to be in the trocla-hiera-backend

diff --git a/lib/puppet/functions/trocla_lookup_key.rb 
b/lib/puppet/functions/trocla_lookup_key.rb
index d377ec8..f61df46 100644
--- a/lib/puppet/functions/trocla_lookup_key.rb
+++ b/lib/puppet/functions/trocla_lookup_key.rb
@@ -33,6 +33,8 @@ Puppet::Functions.create_function(:trocla_lookup_key) do
   trocla_hierarchy(trocla_key, format, opts)
 end
 
+@trocla.close

+
 context.not_found unless res
 context.cache(key, res)
   end


Le 18/10/2017 à 10:01, Poil a écrit :

Hi,

There still a leak on Trocla database connections (latest 
gem/module/hiera backend).


I've installed a puppetserver, with only a node connected on; after 5 
days, there is 240 opened connections.


Best regards,


Le 16/10/2017 à 09:44, Poil a écrit :

Hi,

We have upgrade to Hiera Backend v5 (and to the new trocla v5 backend)

There still a leak but it seems to be very very low.

I've also switched in our site.pp all hiera/hiera_hash/hiera_array 
call to lookup. We still have some hiera* function call in some 
module, I'm asking myself if the leak is not in these functions.


Best regards,


Le 06/10/2017 à 12:40, Poil a écrit :

Hi,

The database connections leak remains after upgrading trocla.
Also after 2 days the catalog computation times start to increase 
again.
I'm going to install newrelic on a puppetserver and if I see nothing 
I will try to analyze via your blog article.


Best regardsLe 4 oct. 2017 10:58, Poil  a écrit :

Hi,

Thanks !

We had Trocla 0.2.3, and module 0.2.2 I'm upgrading to Trocla 0.3.0 
and

latest module code

Best regards,


Le 04/10/2017 à 08:27, Peter Meier a écrit :

We are on hiera v3, we only tuned "max-requests-per-instance: 5000"
because of a databases connection leak with our Trocla library.
This is fixed with the trocla module 1.0.1 [1] are you on that 
version?


best

~pete

[1]
https://github.com/duritong/puppet-trocla/commit/bbedb788a7951e2f69c1c2815a5c3c669ff02ae6 




--
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/675be630-3ef4-e316-6d05-d6000eaadd6c%40quake.fr.

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/a1bca6b3-5824-b97f-117f-95f22c7588ab%40quake.fr.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] PuppetServer 2.8 resource Leak

[Poil]

Hi,

There still a leak on Trocla database connections (latest 
gem/module/hiera backend).


I've installed a puppetserver, with only a node connected on; after 5 
days, there is 240 opened connections.


Best regards,


Le 16/10/2017 à 09:44, Poil a écrit :

Hi,

We have upgrade to Hiera Backend v5 (and to the new trocla v5 backend)

There still a leak but it seems to be very very low.

I've also switched in our site.pp all hiera/hiera_hash/hiera_array 
call to lookup. We still have some hiera* function call in some 
module, I'm asking myself if the leak is not in these functions.


Best regards,


Le 06/10/2017 à 12:40, Poil a écrit :

Hi,

The database connections leak remains after upgrading trocla.
Also after 2 days the catalog computation times start to increase again.
I'm going to install newrelic on a puppetserver and if I see nothing 
I will try to analyze via your blog article.


Best regardsLe 4 oct. 2017 10:58, Poil  a écrit :

Hi,

Thanks !

We had Trocla 0.2.3, and module 0.2.2 I'm upgrading to Trocla 0.3.0 and
latest module code

Best regards,


Le 04/10/2017 à 08:27, Peter Meier a écrit :

We are on hiera v3, we only tuned "max-requests-per-instance: 5000"
because of a databases connection leak with our Trocla library.
This is fixed with the trocla module 1.0.1 [1] are you on that 
version?


best

~pete

[1]
https://github.com/duritong/puppet-trocla/commit/bbedb788a7951e2f69c1c2815a5c3c669ff02ae6 




--
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/675be630-3ef4-e316-6d05-d6000eaadd6c%40quake.fr.

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/17920f2d-5028-04c7-d389-c093be441ea5%40quake.fr.
For more options, visit https://groups.google.com/d/optout.