Re: [Puppet Users] Is there a solid EOL date for the Puppet 3.8 release family?

[Carthik Sharma]

HI Trevor,

For PE, this page might help:
https://puppetlabs.com/misc/puppet-enterprise-lifecycle
For the agent, the EOL depends on the end of official support for the
platform itself, see:
https://docs.puppetlabs.com/guides/platforms.html#puppet-agent-and-operating-system-support-life-cycles

I am sure someone will correct me if that is wrong.

Thanks,
Carthik.

On Wed, Mar 9, 2016 at 12:15 PM, Trevor Vaughan 
wrote:

> I've had a few questions and I realized that I didn't actually know.
>
> Thanks,
>
> Trevor
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
>
> -- This account not approved for unencrypted proprietary information --
>
> --
> 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/CANs%2BFoWbfYDC5hjWwqRtkKQFsWi5A5Qrn%3DheHgkuRwMPN7ZQsA%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/CAOzFSfFMRdpvGewkwagB%3DWTSF2YOOqpn%3DA4q6BworVn0_2j3LA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] tidy - remove all files matching a pattern, except the most recently modified file

[Carthik Sharma]

Is the most-recently-modified file a resource managed by puppet? If so, you
can use tidy with recurse, and tidy will not clean up the managed file.


On Tue, Mar 15, 2016 at 4:01 AM, Tony Gaetani 
wrote:

> I would like to have a tidy resource that deletes all files recursively
> from directories matching a pattern, except for the most recently modified
> file.
>
>
> Something like this:
>
>
> tidy {
>   'clean up files except most recently modified one':
> path => '/path/to/files',
> recurse => true,
> rmdirs => true,
> age => '1h',
> matches => 'some-pattern',
> unless => '{bash script returning most recently modified file name}',
>   ;
> }
>
>
> I understand that this is really stretching the scope of what tidy is for.
> That is why I have decided to just use an exec with a long line of bash
> that does what I want. However, this long and complicated line of bash code
> is not ideal for me because it is hard to understand and maintain, it's
> just kind of ugly:
>
>
> # 1 - find all directories matching a pattern, print the most recently
> modified time and path
> # 2 - sort by most recently modified
> # 3 - remove the timestamp
> # 4 - remove the last item
> # 5 - rm -rf all of the paths
> find /path/to/files -maxdepth 1 -type d -name 'some*pattern' -printf '%T+
> %p\n' | sort | cut -d' ' -f2 | head -n -1 | xargs rm -rf
>
>
> Even if tidy is not an option, does anyone else have any better ideas than
> my exec?
>
> Thanks in advance
> -Tony
>
> --
> 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/3962a82f-536a-49ef-ad57-ddd872d4ba6f%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/CAOzFSfFCbzkWmvczd%2B-AGLN9z%3Dbw3brkZW1puZtGR2_zkNVDww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppet catalog compilation job queue idea

[Eric Sorenson]

The first and most significant chunk of the direct puppet work, namely a 
production-ready version of "static catalogs" is going out in Puppet 4.4.0. 
You can preview the documentation for it 
here: 
https://github.com/puppetlabs/puppet-docs/blob/master/source/puppet/4.4/reference/static_catalogs.md

Future work is around the other stuff you mentioned - especially 
precompilation. 

--eric0

On Tuesday, March 8, 2016 at 7:02:40 AM UTC-8, R.I. Pienaar wrote:
>
> I believe the thing thats happening here is called Direct Puppet, there 
> were some puppet conf talks about this you might want to look at the 
> videos. 
>
> But it's around reworking the compile flow so you can pre-compile things, 
> re-run 
> earlier compiled things, redo the static catalogs and even rewriting the 
> compiler 
> in C++ 
>
> There are stuff happening on Jira at the moment, but I'd guess lots of 
> this will 
> be PE only if recent blogs are anything to go by 
>
> - Original Message - 
> > From: "jcbollinger"  
> > To: "puppet-users"  
> > Sent: Tuesday, 8 March, 2016 15:51:31 
> > Subject: Re: [Puppet Users] Re: puppet catalog compilation job queue 
> idea 
>
> > On Monday, March 7, 2016 at 7:57:33 PM UTC-6, SG Madurai wrote: 
> >> 
> >> Hi John, Thank you for the update. 
> >> 
> >> Pardon me if i am asking about things that have been clarified/ settled 
> >> already. 
> >> 
> >> From what i understand, agent run times are primarily determined by 
> >> - catalog compilation time at master 
> >> - the time for agent to apply catalog on its node 
> >> 
> >> 
> > 
> > Both of those are contributors.  The former is rarely a major one. 
>  There 
> > is also time spent by the agent computing facts, which is usually even 
> > less, but can be costly if costly custom facts are installed. 
> > 
> > Also, catalog application often is not an agent-only activity, as it 
> > commonly involves the agent obtaining files from the master's file 
> server. 
> > This can be very expensive for both the agent and the master. 
> > 
> > 
> > 
> >> So was basically wondering if there is an option to separate these 2 
> >> functions and manage these 2 independent of each other (at times 
> convenient 
> >> for each of these activities) 
> >> 
> >> 
> > 
> > Nodes have as much control as they want to exercise of when and how 
> often 
> > they perform catalog runs.  If they run the agent in daemon mode then 
> they 
> > can configure the run interval, but they also have the option of running 
> it 
> > at the times they choose via a scheduler, such as cron, or on-demand 
> either 
> > manually or via a remote-control system such as MCollective. 
> > 
> > The master does perform some caching to speed catalog building, but as I 
> > already said, it is impractical for it to cache whole catalogs for 
> direct 
> > service to clients.  The problem here lies in determining accurately and 
> > efficiently when cached catalogs are stale. 
> > 
> > 
> > 
> >> If these concerns shouldn't arise with running multiple puppet masters 
> w/ 
> >> puppet db (or by imply upgrading...we are on v3.8 btw), then will 
> explore 
> >> that option first. 
> >> 
> > 
> > 
> > If your master(s) do not adequately serve the catalog request load, then 
> > the quickest solution is often to empower them by running more 
> puppetmatser 
> > threads, adding CPU, adding RAM, increasing network bandwidth, and/or 
> > shutting down other services.  "Shutting down other services" might 
> include 
> > moving PuppetDB to a separate machine.  Do also attend to the 
> possibility 
> > of uneven load: some kinds of site configurations lend themselves to 
> highly 
> > uneven load on the master, such that it sometimes gets transiently 
> > overloaded even though it has sufficient capacity for its average load. 
> > 
> > If individual catalog compilations are taking a long time, then it is 
> > probably worthwhile investigating why that is.  It may well be the case 
> > that you can realize substantial improvements by modifying your manifest 
> > set.  If the master is bogged down at the file server then you are 
> probably 
> > managing either large numbers of files or very large files, or both, in 
> an 
> > inefficient way; this is an area where it is relatively easy to shoot 
> > yourself in the foot. 
> > 
> > If none of those alternatives yield the catalog service bandwidth you 
> need, 
> > then the next logical step is multiple masters. 
> > 
> > 
> >> 
> >> I couldn't be sure if these configuration options (multiple puppet 
> masters 
> >> w/ puppet db) by itself can take care of the issues we are facing with 
> >> agent runs  in our environment 
> >> (timeouts, slowness..) 
> >> 
> >> We have one puppet master (v3.8) managing 150-200 nodes in an 
> environment. 
> >> 
> > 
> > 
> > That's a fairly substantial load for a single master, but whether it's 
> at 
> > or beyond the capacity you should expect depends 

[Puppet Users] tidy - remove all files matching a pattern, except the most recently modified file

[Tony Gaetani]

I would like to have a tidy resource that deletes all files recursively 
from directories matching a pattern, except for the most recently modified 
file.


Something like this:


tidy {
  'clean up files except most recently modified one':
path => '/path/to/files',
recurse => true,
rmdirs => true,
age => '1h',
matches => 'some-pattern',
unless => '{bash script returning most recently modified file name}',
  ;
}


I understand that this is really stretching the scope of what tidy is for. 
That is why I have decided to just use an exec with a long line of bash 
that does what I want. However, this long and complicated line of bash code 
is not ideal for me because it is hard to understand and maintain, it's 
just kind of ugly:


# 1 - find all directories matching a pattern, print the most recently 
modified time and path
# 2 - sort by most recently modified
# 3 - remove the timestamp
# 4 - remove the last item
# 5 - rm -rf all of the paths
find /path/to/files -maxdepth 1 -type d -name 'some*pattern' -printf '%T+ 
%p\n' | sort | cut -d' ' -f2 | head -n -1 | xargs rm -rf


Even if tidy is not an option, does anyone else have any better ideas than 
my exec?

Thanks in advance
-Tony

-- 
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/3962a82f-536a-49ef-ad57-ddd872d4ba6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Need hide execution window on Windows Scheduled Tasks

[Jesus Vte. Vila]

Hi, I'm using Puppet Agent 1.3.5 on Windows Server 2008 and 2012.

When I create a Scheduled Task, it creates correctly but every time task is 
running, it shows the task screen. If the task is running every 5 minutes 
it's annoying.

I've observed Puppet Agent, create task and in the properties, in the part 
"Configure for" is selected "Windows Server 2003, Windows XP o Windows 2000"

If i change this for "Windows Vista or Windows 2008" the window of the 
running task is hidden :-) but when agent run again, it changes again to 
Windows 2003 

What can i do?

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/66393c2c-a952-401a-9526-a88d4a8295d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: override class attributes

[TimV]

Thank you for the detailed response.


> Side note: class names should not contain hyphens.  It may or may not 
> cause actual breakage in your particular version of Puppet, but I advise 
> you to change it to an underscore, or to simply remove it.
>
>
noted. I'll update the name.
 

>  
>
>> Puppet apply run's ok, but IPtables never changes.  The default rule 
>> 0050, stays as
>> accept.
>>
>
>
> Although one of the options for declaring classes has a syntax like that 
> of a resource declaration, and although Puppet's catalog builder accepts 
> declarations that purport to override class parameters via the 
> resource-parameter override syntax, such class parameter overrides are not 
> useful.  I almost wrote "not effective", but that's actually a open to 
> interpretation.  This is the subject of PUP-1367 
> , but you really ought to 
> read the (extended) discussion associated with the equivalent ticket in 
> the old bug tracker .  There 
> is a lot of good information there, but I draw your attention specifically 
> the exchange between Luke Kanies and myself, starting at comment #35.  Here 
> are a few highlights:
>
>
I'll take a look, but I am sure it's over my head.
 

> Since its introduction in Puppet 3.0, automatic data binding (via Hiera) 
> has been the best mechanism for assigning non-default values to the 
> parameters of any and every module's public classes.  Relying on data 
> binding solves several kinds of problems, including yours.  In fact, yours 
> is the bread & butter use case for data binding; I'm more used to arguing 
> others of its merits.  If your manifest set is not built with automated 
> data binding in mind, however, then it might require an uncomfortable 
> amount of reorganization to take advantage of it.
>
> I also noticed with puppet-lint this warning:
>> class inherits across module namespaces
>>
>>
>>
>> Is this because I am overriding a class that references another class 
>> (firewall)?
>>
>
>
> It is because a class belonging to one module (lib-wordpress) inherits 
> from a class belonging to a different module (apache).  This is allowed, 
> but it is widely considered poor form, because it creates an 
> inappropriately strong coupling between the modules involved.  If you use 
> data binding effectively then you do not need to do this sort of thing.
>
>  
>

Strongly coupled modules are bad. I understand this.
 

> If 
>> so, how should I avoid this? I might be running up against this bug:
>>
>>> Note: If a base class declares other classes with the resource-like 
 syntax, a class derived from it cannot override the class parameters of 
 those inner classes. This is a known bug.

>>>
>>
>
> Yes, that seems to be describing PUP-1367, but it's a bit off.  In the 
> first place, the problem has nothing directly to do with the syntax used by 
> the parent class to declare the class whose parameters you hope to be able 
> to override.  Use of the resource-like syntax simply tends to give the 
> impression that an override should work.  In fact, at least in some Puppet 
> versions, it *does* work, in the sense that from Puppet's perspective, 
> the parameter values indeed are changed.  The root of the problem, however, 
> is that such changes take effect too late to make any practical difference 
> in the catalog that is produced.  That's why I was careful to say at the 
> beginning that such overrides are "not useful".
>
> In the second place, the summary gives the impression that the bug is in 
> the fact that the parameter overrides do not have the desired effect.  This 
> is by no means settled, and that may be why the issue is still open.  I'm 
> inclined to say (and *did* say among my comments on the issue) that the 
> bug is that the existence of resource-like class declaration syntax 
> promotes the false expectation that overrides will have an observable 
> effect on the catalog, and in the fact that the catalog builder accepts the 
> declarations without even a warning.
>
>
> John
>
>
Again, thanks for the reply. If I understand you correctly, trying to 
accomplish an override such as I've setup, is a mixed bag - it might work, 
but it's generally not the correct way to do things.
Looking forward, I should take advantage of modules that utilize automatic 
data binding via hiera, and/or write my modules with this in mind.

As it stands currently, what I am trying to do won't work (at least 
reliably)?

 

-- 
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/a24187c3-4d1a-406b-8647-df5ede4891a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Options for notifying external services in case of changing exported resources.

[jcbollinger]

On Monday, March 14, 2016 at 11:23:53 AM UTC-5, Jelle Smet wrote:
>
> Hi list,
>
>
> I have a Puppet module (internal to the company) which makes use of 
> exported resources.
> The exported resource data stored in PuppetDB is used to configure an 
> external application.
>


That sounds like an odd way to go about it.  One would normally export 
resources that directly configure the external application, one way or 
another.  Details vary greatly with nature of the application that needs to 
be configured, of course.

 

>
> I'm looking for a way to notify this external service in order to trigger 
> it load the stored exported resources from PuppetDB.
> If the "trigger" would be a log (syslog) event that would already be 
> sufficient to work with.
>
> I have found 3 ways to achieve this, but for different reasons I'm not 
> allowed to use them:
>
>
>1. Use a Postgress trigger on the PuppetDB database which generates an 
>event in case data changes.
>
>2. https://github.com/ryanuber/puppet-tell.
>
>3. An exec of the "/usr/bin/logger" command with "*refreshonly*" which 
>subscribes to a a file resource writing the exported resources to a file.
>The data written to the file would then have to be the same as the 
>exported resources.
>This would mean, if the "exported resources"  change, the content of 
>the file changes which only then produce a syslog.
>
> Unfortunately, the notify resource doesn't support "*refreshonly*".
>
>
> Are there any other constructions which would allow me to notify an 
> external application in case exported resources for a host have changed?
>
>

So that we do not waste our time suggesting other non-viable alternatives, 
how about giving us the constraints on what solutions you will be allowed 
to use?

So that we can get a handle on what even to consider, how about describing 
what has to happen to configure the target application?

Without more information, anything we might suggest would be a shot in the 
dark.


John

-- 
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/bb0d92a8-78d9-4e26-aa4c-e51ac0625478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: override class attributes

[jcbollinger]

On Monday, March 14, 2016 at 4:36:18 PM UTC-5, TimV wrote:
>
> Hi -
> I am trying to figure out how to best override
> resource attributes for a module.  I know this might not
> be the best way to do things, but it's where I am at currently.
>
> In summary:
>
>- I have a module called Apache, that references the firewall class 
>from the puppetlabs/firewall module - to open ports 80/443.
>- I have a few nodes, that need wordpress installed (as well as 
>apache) 
>- I need to override the default fw ports 80/443 being opened, for 
>more selective rules.
>
> I am trying to override these resources similar to what is described here:
>
> https://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#overriding-resource-attributes
>
> Here's my code:
>
> nodes.pp
>   node 'wordpress-dev.blah.example.com' {
> include base
> include users
> include webteam
> include apache
> include libfw::wordpress
> group { 'webteam':
>   ensure  => present,
>   name=> 'webteam',
>   members => 'sdf, sdf1, sdf3, sdf4'
> }
> include basicfw
> include lib-wordpress
> include wordpress_cli
> include php
> }
>
>
>
> Apache and wordpress are two very basic modules I wrote. 
>
> apache::config
> apache::config has the following:
> class apache::config {
>   firewall { '0050 allow http and https access':
> chain  => 'LSO-Firewall-1-INPUT',
> dport  => [80, 443],
> proto  => tcp,
> action => accept,
>   }
> }
>
>
> Then in the wordpress module, I am trying to override this setting with:
>
> lib-wordpress::config
> class lib-wordpress::firewall inherits apache::config {
>   Class['apache::config'] {
> chain  => 'LSO-Firewall-1-INPUT',
> dport  => [80, 443],
> proto  => tcp,
> action => reject,
>   }
> }
>
>

Side note: class names should not contain hyphens.  It may or may not cause 
actual breakage in your particular version of Puppet, but I advise you to 
change it to an underscore, or to simply remove it.

 

> Puppet apply run's ok, but IPtables never changes.  The default rule 0050, 
> stays as
> accept.
>


Although one of the options for declaring classes has a syntax like that of 
a resource declaration, and although Puppet's catalog builder accepts 
declarations that purport to override class parameters via the 
resource-parameter override syntax, such class parameter overrides are not 
useful.  I almost wrote "not effective", but that's actually a open to 
interpretation.  This is the subject of PUP-1367 
, but you really ought to 
read the (extended) discussion associated with the equivalent ticket in the 
old bug tracker .  There is a 
lot of good information there, but I draw your attention specifically the 
exchange between Luke Kanies and myself, starting at comment #35.  Here are 
a few highlights:

Me:

> It was a mistake to shift toward casting classes as resources, and the 
> whole community, including PL, will be well served by re-establishment of a 
> clear distinction.
>

That trend and practice has since largely been reversed.

Luke:

> You’re right that it’s basically impossible to escape pathological cases.
>

He goes on, however, to suggest implementing a scheme that he believed 
would work in most cases.  As far as I am aware, no such change has ever 
been released.

My own opinion at the time was:

> I think it’s a harder problem than you appreciate, and that it’s not just 
> pathological cases that will prove difficult.
>

And to bring it back around to the present question, I predicted:

> [T]his is going to continue to be a sore spot as long as the structure of 
> the language inclines people to believe that it *should* work, all 
> documentation notwithstanding. Indeed, if the structure of the language 
> leads people to erroneously believe it should work, then that’s a flaw of 
> its own in the language design.
>

It's not now as sore as I then thought it would be, but that's to some 
extent because resource overrides through class inheritance have largely 
fallen out of favor.  Indeed, inasmuch as the whole purpose of class 
inheritance was originally to provide for such overrides, class inheritance 
itself is now widely frowned upon, except for use of one of its side 
effects to implement the Params Class pattern.

Since its introduction in Puppet 3.0, automatic data binding (via Hiera) 
has been the best mechanism for assigning non-default values to the 
parameters of any and every module's public classes.  Relying on data 
binding solves several kinds of problems, including yours.  In fact, yours 
is the bread & butter use case for data binding; I'm more used to arguing 
others of its merits.  If your manifest set is not built with automated 
data binding in mind, however, then it might require an uncomfortable 
amount of reorganization to take advantage of it.

I also noticed with 

Re: [Puppet Users] PuppetDB: Input to insert-facts-pv-pairs! does not match schema

[Akos Hencz]

Hi Wyatt,

Thank you for the help!

>From the DLO entries I could get the exact command payload and found a 
malformed structured fact. It had a nested dictionary, where most entries 
were formed "foo" => "bar", except for one that looked like  
"\"foo"=>"bar\"".
After fixing this, the node managed to successfully send its facts to 
PuppetDB.

Cheers,
Akos

On Monday, March 14, 2016 at 4:54:26 PM UTC+1, Wyatt Alt wrote:
>
> On 03/14/2016 06:34 AM, Akos Hencz wrote:
>
> Hello,
>
> We have a few nodes that fail to submit facts to PuppetDB, and the replace 
> facts commands end up in the DLO. The exception is: 
> clojure.lang.ExceptionInfo: Input to insert-facts-pv-pairs! does not match 
> schema.
> I suspect it is a problem with one of the facts, but I cannot determine 
> which one. Looking at the output of 'facter -p' on any of the nodes seem to 
> be fine. 
>
> I would like to ask for some advice on how to investigate the cause of 
> this problem. :)
>
> We run Puppet 3.8.4, PuppetDB 2.3.4, and PuppetServer 1.1.3. You can see 
> the full exception text below.
>
> Cheers,
> Akos
>
>
> clojure.lang.ExceptionInfo: Input to insert-facts-pv-pairs! does not match 
> schema: [nil (named (not (some (check % a-clojure.lang.LazySeq) schemas)) 
> pairs)] {:error [nil (named (not (some (check % a-clojure.lang.LazySeq) 
> schemas)) pairs)], :value [44289 ([17 954] [90 58] [100 207518370] [147 
> 137] [72 86] [96 274005961] [49 207518365] [31 57830745] [152 1307] [48 
> 928] [104 295874761] [81 21735] [167 302087295] [162 167699] [68 25] [1 
> 826] [57 23] [119 291018089] [12 302087311] [7 912] [139 193] [134 539] 
> [205 28] [137 1299] [34 49] [18 200] [4 7644696] [14 7] [35 59021633] [1526 
> 302087296] [58 73] [120 830] [163 65] [178 1293] [80 870] [1527 302087294] 
> [95 274005961] [40 157758900] [77 302087312] [116 101387066] [111 112] [41 
> 57830745] [269911 302087303] [269910 193] [269912 57830745] [269909 
> 57830745] [269908 57830745] [269914 57830745] [269913 302087292] [195 65] 
> [1248 207518367] [2472 800] [2487 136] [2489 765] [2491 488] [2467 
> 207518365] [2478 830] [2485 800] [2475 207518370] [2496 793] [2501 
> 207518365] [2486 765] [2466 488] [93 302087302] [126 136] [23 105] [15 
> 50105231] [115 110] [136 299] [121 800] [129 57830729] [56 232889320] 
> [56434 8543] [276 939] [70 75] [106 302087301] [98 229] [110 57830742] [45 
> 67] [24 883] [107 904] [124 182796497] [99 89] [47985 302087314] [47983 
> 81057077] [47982 223071] [47989 294247] [47988 492094] [47991 82005831] 
> [47987 228539865] [47986 81057081] [47990 136333789] [47984 137976183] 
> [49100 563] [49098 82071940] [49093 136059519] [49095 108941256] [49116 
> 82065378] [49114 82063765] [49118 82063767] [49117 82063764] [49121 
> 82063916] [49120 16973] [49115 63121] [49119 88397486] [49150 82064260] [66 
> 302087301] [5 302087302] [63 31] [37 287849745] [51 25] [28 302087305] [73 
> 3927] [485 28] [59 125] [13 302087310] [91 780] [54 94] [127 299] [11 765] 
> [1528 488] [156 65] [215 28] [239 302087304] [21 295871169] [38 302087315] 
> [25 882] [114 17] [101 57830743] [86 57830733] [39 302087308] [297092 
> 195213941] [131 302087293] [130 802] [22 923] [1246 302087313] [2494 
> 302087300] [2462 68508392] [2473 57830743] [2457 3927] [67 1326] [133 
> 302087305] [71 136778] [65 207518365] [2 169693143] [103 167718] [19 763] 
> [1529 302087289] [2461 28] [2453 302087302] [2500 200] [2458 21735] [2493 
> 302087302] [2477 295871174] [2464 200] [2492 539] [2459 8224991] [2476 
> 167718] [2483 38] [2495 302087291] [2451 136778] [2460 91] [2488 17] [2454 
> 67] [2469 112] [2463 302087305] [2470 302087302] [141 1317] [88 302087297] 
> [52 929] [1250 8224986] [53 302087300] [123 46] [75 302087307] [135 
> 57830744] [2246 302087298] [2471 302087309] [2455 539] [2452 302087302] 
> [2465 188476291] [2484 188476291] [nil 302087288] [2497 1326] [2590 
> 302087290] [2498 302087311] [33 25] [83 302087305] [79 87] [89 38] [188 
> 140] [69 169693143] [8 302087306] [122 13] [140 1283] [84 94] [1249 
> 295871170] [2479 295871169] [2525 295871169] [2474 59021633] [2468 
> 59021633] [164 65] [92 295871169] [456928 36] [6 1608] [248 302087299] [16 
> 57830733] [1015 104292798] [174 236] [128 302087302] [20 68508392] [102 
> 765] [113 793] [125 80] [26 765] [118 101387069] [9 296645235] [30 290] 
> [108 800] [76 302087302] [183 44875635] [158 296658966] [1530 8224991] [278 
> 938] [29 295871174] [10 91] [105 302087291] [27 302087302] [142 181] 
> [263862 302087287] [50 67] [196 167697] [1531 268074168] [2482 266778936] 
> [2490 57830732] [2499 116471] [2481 929] [109 928] [43 2780] [146 65] [1532 
> 31] [97 59021633] [36 67] [254 28] [3 1671] [87 200] [62 802] [181 912] 
> [191 1299] [74 904] [60 57830733] [44 302087297] [94 296930720] [85 
> 59021638])], :schema [#schema.core.One{:schema Int, :optional? false, :name 
> factset-id} #schema.core.One{:schema (either [[(one Int "path-id") (one Int 
> "value-id")]] #{[(one Int "path-id") (one Int "value-id")]}), 

Re: [Puppet Users] directory environemnt doesn't seem to be working for vcsrepo

[Luke Bigum]

The error itself is quite clear - you've got an empty string for the parameter 
'revision' when you should have something that's not whitespace (according to 
that regex).

To actually figure out why you're getting an empty string, you're going to need 
to post the relevant portions of app.pp (or it's entirety).

--
Luke Bigum

- Original Message -
From: "Sans" 
To: "puppet-users" 
Sent: Monday, 14 March, 2016 21:40:34
Subject: [Puppet Users] directory environemnt doesn't seem to be working for 
vcsrepo

Hi there ,

I'm seeing a very strange error, which I cannot figure out where it's 
coming from:


*Error: Failed to apply catalog: Parameter revision failed on 
Vcsrepo[/var/www/wp007/wp-content]: Invalid value "". Valid values match 
/^\S+$/. at /usr/local/p19/puppet/modules/wordpress/manifests/app.pp:163*


Line #163  is where I specified the vcsrepo to do the git pull from staging 
branch. I cannot get any other info using -td or --trace. Any one has seen 
this error before or know what's going on?
Just to give you a but of background, the PuppetMaster is running with two 
environments: development and staging, with directory environment enabled. 
This error is coming from the staging instances.  Is it possible it's not 
getting the environment specific values to compile the catalog? Hoe do I do 
further debugging? 

Got really stuck in the middle, so nay help will be appreciated.

-San

-- 
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/13af960b-eaa6-4944-9800-b36a4ebb0e4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
---

LMAX Exchange, Yellow Building, 1A Nicholas Road, London W11 4AN
http://www.LMAX.com/

Recognised by the most prestigious business and technology awards
 
2016 Best Trading & Execution, HFM US Technology Awards
2016, 2015, 2014, 2013 Best FX Trading Venue - ECN/MTF, WSL Institutional 
Trading Awards

2015 Winner, Deloitte UK Technology Fast 50
2015, 2014, 2013, One of the UK's fastest growing technology firms, The Sunday 
Times Tech Track 100
2015 Winner, Deloitte EMEA Technology Fast 500
2015, 2014, 2013 Best Margin Sector Platform, Profit & Loss Readers' Choice 
Awards

---

FX and CFDs are leveraged products that can result in losses exceeding your 
deposit. They are not suitable for everyone so please ensure you fully 
understand the risks involved.

This message and its attachments are confidential, may not be disclosed or used 
by any person other than the addressee and are intended only for the named 
recipient(s). This message is not intended for any recipient(s) who based on 
their nationality, place of business, domicile or for any other reason, is/are 
subject to local laws or regulations which prohibit the provision of such 
products and services. This message is subject to the following terms 
(http://lmax.com/pdf/general-disclaimers.pdf), if you cannot access these, 
please notify us by replying to this email and we will send you the terms. If 
you are not the intended recipient, please notify the sender immediately and 
delete any copies of this message.

LMAX Exchange is the trading name of LMAX Limited. LMAX Limited operates a 
multilateral trading facility. LMAX Limited is authorised and regulated by the 
Financial Conduct Authority (firm registration number 509778) and is a company 
registered in England and Wales (number 6505809).

LMAX Hong Kong Limited is a wholly-owned subsidiary of LMAX Limited. LMAX Hong 
Kong is licensed by the Securities and Futures Commission in Hong Kong to 
conduct Type 3 (leveraged foreign exchange trading) regulated activity with CE 
Number BDV088.

-- 
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/1424013521.5311651.1458031228363.JavaMail.zimbra%40lmax.com.
For more options, visit https://groups.google.com/d/optout.