Re: [Puppet Users] finished, yet execution expired
In my case is also happening with 2.6.8. making async_storeconfigs=false Seemed to resolve the issue. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ymllookup is a wonderful thing
Looks like fun, although the feature I really, really wanted seems to be held up by parser issues. The lookups work great, but at least in 2.6.7 my arrays of hashes fall over pretty regularly with pson errors when I try to use them as resource names. If it were me I'd replace the to_s with a numeric representation of the hash contents so that it would work properly as $name in resources and defines. In my use case I could care less about the name of the object, I really just want access to the key=>value pairs it contains. On Fri, May 27, 2011 at 2:09 PM, R.I.Pienaar wrote: > And for those who have been following ticket 6079 and Nigels > get() function this version of extlookup now has 1:1 feature parity > with that and a Puppet backend. > > In addition I've extended Nigels work to also support precedence like > normal with extlookup > > - Original Message - > > And for what its worth this afternoon just to see how hard it is > > and to again ask to myself 'wtf has no-one done this yet?' and also > > 'wtf are people at Puppet Labs reinventing this wheel?' I wrote > > a new extlookup that has pluggable backends. > > > > It has a 100% backward compatible CSV backend and new a YAML backend > > > > Backends are easy to add - I will make the interface a little bit > > better > > in future and I, again, wish Puppet Labs would fix bugs that make it > > easier to deploy Util classes into masters. > > > > Rather than abuse global variables I added a simple YAML based config > > file. > > > > So, again, I hacked this up this afternoon, its early days and no > > doubt > > can be improved. Feedback welcome > > > > https://github.com/ripienaar/puppet-extlookup > > > > - Original Message - > > > Thanks Ohad, this looks very interesting. > > > > > > > > > On Fri, May 27, 2011 at 11:07 AM, Ohad Levy < ohadl...@gmail.com > > > > wrote: > > > > > > > > > > > > fyi, https://github.com/ohadlevy/puppet-lookup exists for a long > > > time > > > too, it also allows you to put your actual data files inside your > > > modules (or mulitple modules with a search / prio path). > > > > > > > > > Ohad > > > > > > > > > > > > > > > > > > On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell < > > > aaron.grew...@gmail.com > wrote: > > > > > > > > > > > > > > > > > > FYI, if you haven't seen ymllookup it's unofficial but worth a > > > test: > > > http://projects.puppetlabs.com/issues/4433 > > > > > > For those of us that find extlookup useful ymllookup takes it to > > > the > > > next level and allows lookups in YAML. Having the ability to lookup > > > arrays of hashes has made life so much easier for me. > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Puppet Users" group. > > > To post to this group, send email to puppet-users@googlegroups.com > > > . > > > To unsubscribe from this group, send email to > > > puppet-users+unsubscr...@googlegroups.com . > > > For more options, visit this group at > > > http://groups.google.com/group/puppet-users?hl=en . > > > > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Puppet Users" group. > > > To post to this group, send email to puppet-users@googlegroups.com > > > . > > > To unsubscribe from this group, send email to > > > puppet-users+unsubscr...@googlegroups.com . > > > For more options, visit this group at > > > http://groups.google.com/group/puppet-users?hl=en . > > > > > > > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Puppet Users" group. > > > To post to this group, send email to puppet-users@googlegroups.com. > > > To unsubscribe from this group, send email to > > > puppet-users+unsubscr...@googlegroups.com. > > > For more options, visit this group at > > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > > -- > > R.I.Pienaar > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > R.I.Pienaar > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://g
Re: [Puppet Users] ymllookup is a wonderful thing
And for those who have been following ticket 6079 and Nigels get() function this version of extlookup now has 1:1 feature parity with that and a Puppet backend. In addition I've extended Nigels work to also support precedence like normal with extlookup - Original Message - > And for what its worth this afternoon just to see how hard it is > and to again ask to myself 'wtf has no-one done this yet?' and also > 'wtf are people at Puppet Labs reinventing this wheel?' I wrote > a new extlookup that has pluggable backends. > > It has a 100% backward compatible CSV backend and new a YAML backend > > Backends are easy to add - I will make the interface a little bit > better > in future and I, again, wish Puppet Labs would fix bugs that make it > easier to deploy Util classes into masters. > > Rather than abuse global variables I added a simple YAML based config > file. > > So, again, I hacked this up this afternoon, its early days and no > doubt > can be improved. Feedback welcome > > https://github.com/ripienaar/puppet-extlookup > > - Original Message - > > Thanks Ohad, this looks very interesting. > > > > > > On Fri, May 27, 2011 at 11:07 AM, Ohad Levy < ohadl...@gmail.com > > > wrote: > > > > > > > > fyi, https://github.com/ohadlevy/puppet-lookup exists for a long > > time > > too, it also allows you to put your actual data files inside your > > modules (or mulitple modules with a search / prio path). > > > > > > Ohad > > > > > > > > > > > > On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell < > > aaron.grew...@gmail.com > wrote: > > > > > > > > > > > > FYI, if you haven't seen ymllookup it's unofficial but worth a > > test: > > http://projects.puppetlabs.com/issues/4433 > > > > For those of us that find extlookup useful ymllookup takes it to > > the > > next level and allows lookups in YAML. Having the ability to lookup > > arrays of hashes has made life so much easier for me. > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com > > . > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com . > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en . > > > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com > > . > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com . > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en . > > > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/puppet-users?hl=en. > > > > -- > R.I.Pienaar > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Concat Module posted to Onyx Point Github.
Hi Larry, Unfortunately, no. We didn't implement a insync? check since we just needed to overwrite the target files anyway. This is something that appears to be on the todo list as Puppet Labs pulls this into the core. We might beat them to it, but it's doubtful at this time. Thanks! Trevor On Wed, May 25, 2011 at 10:52 PM, Larry Ludwig wrote: > Hi Trevor > Thanks for the module. > > I've been testing out the concat module, thanks, but the only issue I see is > files keep getting 'executed successfully' each round. > Is there any way to not have it do this? I haven't really looked that your > ruby logic yet. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ymllookup is a wonderful thing
And for what its worth this afternoon just to see how hard it is and to again ask to myself 'wtf has no-one done this yet?' and also 'wtf are people at Puppet Labs reinventing this wheel?' I wrote a new extlookup that has pluggable backends. It has a 100% backward compatible CSV backend and new a YAML backend Backends are easy to add - I will make the interface a little bit better in future and I, again, wish Puppet Labs would fix bugs that make it easier to deploy Util classes into masters. Rather than abuse global variables I added a simple YAML based config file. So, again, I hacked this up this afternoon, its early days and no doubt can be improved. Feedback welcome https://github.com/ripienaar/puppet-extlookup - Original Message - > Thanks Ohad, this looks very interesting. > > > On Fri, May 27, 2011 at 11:07 AM, Ohad Levy < ohadl...@gmail.com > > wrote: > > > > fyi, https://github.com/ohadlevy/puppet-lookup exists for a long time > too, it also allows you to put your actual data files inside your > modules (or mulitple modules with a search / prio path). > > > Ohad > > > > > > On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell < > aaron.grew...@gmail.com > wrote: > > > > > > FYI, if you haven't seen ymllookup it's unofficial but worth a test: > http://projects.puppetlabs.com/issues/4433 > > For those of us that find extlookup useful ymllookup takes it to the > next level and allows lookups in YAML. Having the ability to lookup > arrays of hashes has made life so much easier for me. > > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com . > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en . > > > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com . > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en . > > > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Schedule resource oddities (#7639)
The schedule resource has some behavior that comes across as a little...strange. For example: * If you specify a range of "02:00:00 - 01:00:00", Puppet will fail with "Parameter range failed: Invalid range 02:00:00 - 01:00:00; ranges cannot span days.". * If you specify "01:30:00 - 01:00:00", then it is allowed and you get an info message stating "Assuming upper limit should be that time the next day". These seem completely contradictory (and the auto-conversion doesn't seem very useful given it looks like it will end up with a schedule that will _always_ allow application). There's another oddity in that if you don't specify the minutes/seconds then they will default to whatever the _current_ minutes/seconds are on the master. It seems like they should default to zero, instead. Given these things, it seems like we should remove the "Assuming upper limit should be that time the next day" behavior entirely, and defaulting the missing time components to zero instead of to whatever the current value is for the server. If these changes would break how you're using schedules, please let us know (here, or on the related ticket[1]) and please let us know why. [1] http://projects.puppetlabs.com/issues/7639 -- Jacob Helwig signature.asc Description: Digital signature
Re: [Puppet Users] ymllookup is a wonderful thing
Thanks Ohad, this looks very interesting. On Fri, May 27, 2011 at 11:07 AM, Ohad Levy wrote: > fyi, https://github.com/ohadlevy/puppet-lookup exists for a long time too, > it also allows you to put your actual data files inside your modules (or > mulitple modules with a search / prio path). > > Ohad > > On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell wrote: > >> FYI, if you haven't seen ymllookup it's unofficial but worth a test: >> http://projects.puppetlabs.com/issues/4433 >> >> For those of us that find extlookup useful ymllookup takes it to the next >> level and allows lookups in YAML. Having the ability to lookup arrays of >> hashes has made life so much easier for me. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ymllookup is a wonderful thing
fyi, https://github.com/ohadlevy/puppet-lookup exists for a long time too, it also allows you to put your actual data files inside your modules (or mulitple modules with a search / prio path). Ohad On Fri, May 27, 2011 at 7:30 PM, Aaron Grewell wrote: > FYI, if you haven't seen ymllookup it's unofficial but worth a test: > http://projects.puppetlabs.com/issues/4433 > > For those of us that find extlookup useful ymllookup takes it to the next > level and allows lookups in YAML. Having the ability to lookup arrays of > hashes has made life so much easier for me. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Dashboard and GDGraph and or data visualization module
On Wed, Apr 27, 2011 at 10:34 AM, Aaron Lippold wrote: > I was wondering if anyone has started on looking at a general data > graphing framework for visualizing data ( classes, facts, reports ) on > dashboard. > > In the past I have used GDGraph to do this. Has the community talked > about how we want to generalize this for the dashboard? Aaron, I haven't. The new summary reporting going into Dashboard 1.2 is very simple, and a graph library is overkill. In the future we hope to do more, though. What particular things are you looking to graph? r -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet-dev] testing new puppet versions - was Re: [Puppet Users] enabling of 'thin_storeconfigs'
On Fri, May 27, 2011 at 9:25 AM, Peter Meier wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi > > >> I'd avoid any version of puppet that ends in a "0" like the plague if > you > >> want stability. > > > > > > The project has been steadily improving in this regard, but it's > definitely > > been a problem. > > > > I have great hopes for 2.7.0 though, and the more people that test out > our > > RCs (hint! hint!) the better it's going to be. > > Awesome would be some kind of script with which I could test the new > release. Something with puppet cucumber, that people could run and that > would simply try to compile all the catalogs for their hosts and maybe > also comparing the catalogs to the ones of the currently installed version. > As far as just testing new versions, the envpuppet script makes this really easy. https://github.com/puppetlabs/puppet/blob/2.7.x/ext/envpuppet You can simply checkout the git repo, and run it "live" out of the repo. I know we've had a few people work on catalog compilation and comparison, I'll let them speak here. Also it could record compile time etc. so we wouldn't fall into another > regression as we did with 2.6.0 > As a note here, we're working on standardized performance testing with a baseline of manifests so we know when we're introducing performance regressions. > > I know more or less how I could do that with puppet-cucumber and R.I.'s > catalog-diff but I lack a bit the time to setup that. But I would > certainly download a tarball and run the script that I only need to > point to my puppet.conf and send the feedback on that. > > I think this could be in general useful for future releases. > > Yeah I know, I'm just throwing in ideas that don't contain actual > code... Sorry. > Ideas are awesome too :) > > ~pete > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk3f0GsACgkQbwltcAfKi3/bNACeOw2bAr+oYL3VGoWZSLJWCpni > bl4AoIx0j7pTlabE4jAkGUEX8hpbxOv0 > =2EUf > -END PGP SIGNATURE- > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To post to this group, send email to puppet-...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > > -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ymllookup is a wonderful thing
FYI, if you haven't seen ymllookup it's unofficial but worth a test: http://projects.puppetlabs.com/issues/4433 For those of us that find extlookup useful ymllookup takes it to the next level and allows lookups in YAML. Having the ability to lookup arrays of hashes has made life so much easier for me. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
testing new puppet versions - was Re: [Puppet Users] enabling of 'thin_storeconfigs'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi >> I'd avoid any version of puppet that ends in a "0" like the plague if you >> want stability. > > > The project has been steadily improving in this regard, but it's definitely > been a problem. > > I have great hopes for 2.7.0 though, and the more people that test out our > RCs (hint! hint!) the better it's going to be. Awesome would be some kind of script with which I could test the new release. Something with puppet cucumber, that people could run and that would simply try to compile all the catalogs for their hosts and maybe also comparing the catalogs to the ones of the currently installed version. Also it could record compile time etc. so we wouldn't fall into another regression as we did with 2.6.0 I know more or less how I could do that with puppet-cucumber and R.I.'s catalog-diff but I lack a bit the time to setup that. But I would certainly download a tarball and run the script that I only need to point to my puppet.conf and send the feedback on that. I think this could be in general useful for future releases. Yeah I know, I'm just throwing in ideas that don't contain actual code... Sorry. ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3f0GsACgkQbwltcAfKi3/bNACeOw2bAr+oYL3VGoWZSLJWCpni bl4AoIx0j7pTlabE4jAkGUEX8hpbxOv0 =2EUf -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Facts are propatating but dont work from within templates and classes
Thank you verymuch,
Goodbye,
Matteo
2011/5/27 Martin Alfke
>
> On May 27, 2011, at 10:36 AM, M C wrote:
>
> > Hi,
> >
> > could you please tell me your client and master .conf configuration?
>
> My test was made on a single node using puppet agent.
> Here is my puppet.conf:
>
> $ cat /etc/puppetlabs/puppet/puppet.conf
> [main]
>vardir = /var/opt/lib/pe-puppet
>logdir = /var/log/pe-puppet
>rundir = /var/run/pe-puppet
>modulepath = /etc/puppetlabs/puppet/modules
>manifest = /etc/puppetlabs/puppet/manifests/site.pp
>user = pe-puppet
>group = pe-puppet
>
> [master]
>certname = puppetmaster.localdomain
>certdnsnames =
> puppet:puppet.localdomain:puppetmaster:puppetmaster.localdomain
>reports = http, store
>reportsurl = http://localhost:3000/reports/
>ssl_client_header = SSL_CLIENT_S_DN
>ssl_client_verify_header = SSL_CLIENT_VERIFY
>
> [agent]
>certname = puppetagent.localdomain
>server = puppetmaster.localdomain
>report = true
>classfile = $vardir/classes.txt
>localconfig = $vardir/localconfig
>graph = true
>pluginsync = true
>
> [development]
>modulepath = /etc/puppetlabs/puppet/environments/development/modules
>manifest =
> /etc/puppetlabs/puppet/environments/development/manifests/site.pp
>
> [testing]
>modulepath = /etc/puppetlabs/puppet/environments/testing/modules
>manifest = /etc/puppetlabs/puppet/environments/testing/manifests/site.pp
>
>
>
> >
> > THanks ,
> > Matteo
> >
> > 2011/5/26 Martin Alfke
> >
> > On May 26, 2011, at 2:50 PM, M C wrote:
> >
> > > Hi, I have a big problem with custom facts. I created a stub module
> with a "lib/facter" directory as stated in the official Puppet
> documentation.
> > > This is the output i get:
> > >
> > > # puppetd -t --pluginsync
> > > info: Retrieving plugin
> > > notice: /File[/var/lib/puppet/lib]/mode: mode changed '755' to '775'
> > > notice: /File[/var/lib/puppet/lib/facter]/ensure: created
> > > notice: /File[/var/lib/puppet/lib/facter/certname.rb]/ensure: defined
> content as '{md5}dd2f6e661ef1d2d29fa068e8a7d4aa19'
> > > notice: /File[/var/lib/puppet/lib/facter/rootdevice.rb]/ensure: defined
> content as '{md5}a19202a1c8e9f3da0f983403e463fd01'
> > > info: Loading downloaded plugin
> /var/lib/puppet/lib/facter/rootdevice.rb
> > > info: Loading downloaded plugin /var/lib/puppet/lib/facter/certname.rb
> > > info: Loading facts in certname
> > > info: Loading facts in rootdevice
> > > info: Loading facts in certname
> > > info: Loading facts in rootdevice
> > > info: Caching catalog for puppet-1306413279
> > > info: Applying configuration version '1306413876'
> > > notice: /Stage[main]/Test/File[/tmp/puppet.test]/ensure: created
> > > notice: Finished catalog run in 16.23 seconds
> > > root@puppet-1306413279:~# cat /tmp/puppet.test
> >
> > what does your file resource and template definition for /tmp/puppet.test
> look like.
> >
> > the following module snippets are working:
> >
> > class mytest {
> >file "/tmp/puppet.test":
> >content => template("mytest/puppet.test.erb")
> >}
> > }
> >
> > cat template/puppet.test.erb
> > Certname: <%= certname %>
> >
> > cat /tmp/puppet.test
> > Certname: localhost.localdomain
> >
> > >
> > > Certname:
> > > (empty string)
> > >
> > > --
> > >
> > > As you can see, I get no output. This is the code of my "certname"
> fact:
> > >
> > > require 'facter'
> > >
> > > Facter.add("certname") do
> > > setcode do
> > > %x{/usr/bin/puppet --configprint certname}.chomp
> > > end
> > > end
> > >
> > > --
> > >
> > > Could you please tell me where is the problem?
> > >
> > > Thank you verymuch,
> > > Matteo
> > >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > > To post to this group, send email to puppet-users@googlegroups.com.
> > > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@go
Re: [Puppet Users] Facts are propatating but dont work from within templates and classes
On May 27, 2011, at 10:36 AM, M C wrote:
> Hi,
>
> could you please tell me your client and master .conf configuration?
My test was made on a single node using puppet agent.
Here is my puppet.conf:
$ cat /etc/puppetlabs/puppet/puppet.conf
[main]
vardir = /var/opt/lib/pe-puppet
logdir = /var/log/pe-puppet
rundir = /var/run/pe-puppet
modulepath = /etc/puppetlabs/puppet/modules
manifest = /etc/puppetlabs/puppet/manifests/site.pp
user = pe-puppet
group = pe-puppet
[master]
certname = puppetmaster.localdomain
certdnsnames =
puppet:puppet.localdomain:puppetmaster:puppetmaster.localdomain
reports = http, store
reportsurl = http://localhost:3000/reports/
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
[agent]
certname = puppetagent.localdomain
server = puppetmaster.localdomain
report = true
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
graph = true
pluginsync = true
[development]
modulepath = /etc/puppetlabs/puppet/environments/development/modules
manifest = /etc/puppetlabs/puppet/environments/development/manifests/site.pp
[testing]
modulepath = /etc/puppetlabs/puppet/environments/testing/modules
manifest = /etc/puppetlabs/puppet/environments/testing/manifests/site.pp
>
> THanks ,
> Matteo
>
> 2011/5/26 Martin Alfke
>
> On May 26, 2011, at 2:50 PM, M C wrote:
>
> > Hi, I have a big problem with custom facts. I created a stub module with a
> > "lib/facter" directory as stated in the official Puppet documentation.
> > This is the output i get:
> >
> > # puppetd -t --pluginsync
> > info: Retrieving plugin
> > notice: /File[/var/lib/puppet/lib]/mode: mode changed '755' to '775'
> > notice: /File[/var/lib/puppet/lib/facter]/ensure: created
> > notice: /File[/var/lib/puppet/lib/facter/certname.rb]/ensure: defined
> > content as '{md5}dd2f6e661ef1d2d29fa068e8a7d4aa19'
> > notice: /File[/var/lib/puppet/lib/facter/rootdevice.rb]/ensure: defined
> > content as '{md5}a19202a1c8e9f3da0f983403e463fd01'
> > info: Loading downloaded plugin /var/lib/puppet/lib/facter/rootdevice.rb
> > info: Loading downloaded plugin /var/lib/puppet/lib/facter/certname.rb
> > info: Loading facts in certname
> > info: Loading facts in rootdevice
> > info: Loading facts in certname
> > info: Loading facts in rootdevice
> > info: Caching catalog for puppet-1306413279
> > info: Applying configuration version '1306413876'
> > notice: /Stage[main]/Test/File[/tmp/puppet.test]/ensure: created
> > notice: Finished catalog run in 16.23 seconds
> > root@puppet-1306413279:~# cat /tmp/puppet.test
>
> what does your file resource and template definition for /tmp/puppet.test
> look like.
>
> the following module snippets are working:
>
> class mytest {
>file "/tmp/puppet.test":
>content => template("mytest/puppet.test.erb")
>}
> }
>
> cat template/puppet.test.erb
> Certname: <%= certname %>
>
> cat /tmp/puppet.test
> Certname: localhost.localdomain
>
> >
> > Certname:
> > (empty string)
> >
> > --
> >
> > As you can see, I get no output. This is the code of my "certname" fact:
> >
> > require 'facter'
> >
> > Facter.add("certname") do
> > setcode do
> > %x{/usr/bin/puppet --configprint certname}.chomp
> > end
> > end
> >
> > --
> >
> > Could you please tell me where is the problem?
> >
> > Thank you verymuch,
> > Matteo
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Dependency of the collection of virtual ressources.
On May 26, 6:14 am, elderdakkar wrote: > Hello > > i'm managing nagios with exported ressources. > i have some @@nagios_host a lot of @@nagios_service ressources. > Collecting the ressouces itself works fine with Nagios_host <<||>> and > Nagios_service <<||>>. > > BUT :D > > i have a "special" nagios configuration layout: every host has its own > cfg file with the depending servicechecks. This means i have ONE file > with one host definition and all checks for this single host. And this > results in one problem on the puppet side: it seems, that > Nagios_service <<||>> locks the config file and the Nagios_host <<||>> > process can't write its config to the same file. The means: the first > run writes some of the exported ressources to the nagios cfg. The > restart of nagios fails, because some of the hosts aren't written to > the cfg. The next run does the rest and nagios restarts successful. > > Is there a way, to force puppet to start the collection of > Nagios_service <<||>> after Nagios_host <<||>> finishes? > Some kind of dependency? > > i already tried chaining like: > Nagios_host <<||>> -> Nagios_service <<||>> , but then the puppetrun > does nothing. I cannot solve your problem, but for the record, the only way I can imagine the exported resource angle factoring into it is if you have a resource title crash among the resources you are trying to collect. Otherwise, you should have the same behavior with collected resources as you would have if you declared all the same resources locally. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Name or service not known issue
On 2011-05-27 10:39, Sumith Sudhakaran wrote: Hi, When I am trying update from puppet client, getting error like blow *err: Could not request certificate: getaddrinfo: Name or service not known puppetd --test output:- err: Could not request certificate: getaddrinfo: Name or service not known Exiting; failed to retrieve certificate and waitforcert is disabled* Seems like you have a name resolution error. Can you ping your server by name? N. Please help to solve the same.. -- /Regards/// / Sumith/// -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Name or service not known issue
Hi, When I am trying update from puppet client, getting error like blow *err: Could not request certificate: getaddrinfo: Name or service not known puppetd --test output:- err: Could not request certificate: getaddrinfo: Name or service not known Exiting; failed to retrieve certificate and waitforcert is disabled* Please help to solve the same.. -- * Regards*** * Sumith** * -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Facts are propatating but dont work from within templates and classes
Hi,
could you please tell me your client and master .conf configuration?
THanks ,
Matteo
2011/5/26 Martin Alfke
>
> On May 26, 2011, at 2:50 PM, M C wrote:
>
> > Hi, I have a big problem with custom facts. I created a stub module with
> a "lib/facter" directory as stated in the official Puppet documentation.
> > This is the output i get:
> >
> > # puppetd -t --pluginsync
> > info: Retrieving plugin
> > notice: /File[/var/lib/puppet/lib]/mode: mode changed '755' to '775'
> > notice: /File[/var/lib/puppet/lib/facter]/ensure: created
> > notice: /File[/var/lib/puppet/lib/facter/certname.rb]/ensure: defined
> content as '{md5}dd2f6e661ef1d2d29fa068e8a7d4aa19'
> > notice: /File[/var/lib/puppet/lib/facter/rootdevice.rb]/ensure: defined
> content as '{md5}a19202a1c8e9f3da0f983403e463fd01'
> > info: Loading downloaded plugin /var/lib/puppet/lib/facter/rootdevice.rb
> > info: Loading downloaded plugin /var/lib/puppet/lib/facter/certname.rb
> > info: Loading facts in certname
> > info: Loading facts in rootdevice
> > info: Loading facts in certname
> > info: Loading facts in rootdevice
> > info: Caching catalog for puppet-1306413279
> > info: Applying configuration version '1306413876'
> > notice: /Stage[main]/Test/File[/tmp/puppet.test]/ensure: created
> > notice: Finished catalog run in 16.23 seconds
> > root@puppet-1306413279:~# cat /tmp/puppet.test
>
> what does your file resource and template definition for /tmp/puppet.test
> look like.
>
> the following module snippets are working:
>
> class mytest {
>file "/tmp/puppet.test":
>content => template("mytest/puppet.test.erb")
>}
> }
>
> cat template/puppet.test.erb
> Certname: <%= certname %>
>
> cat /tmp/puppet.test
> Certname: localhost.localdomain
>
> >
> > Certname:
> > (empty string)
> >
> > --
> >
> > As you can see, I get no output. This is the code of my "certname" fact:
> >
> > require 'facter'
> >
> > Facter.add("certname") do
> > setcode do
> > %x{/usr/bin/puppet --configprint certname}.chomp
> > end
> > end
> >
> > --
> >
> > Could you please tell me where is the problem?
> >
> > Thank you verymuch,
> > Matteo
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Name or service not known
Hi, When I am trying update from puppet client, getting error like blow err: Could not request certificate: getaddrinfo: Name or service not known Please help to solve the same.. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
