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 th
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
nume
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
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
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
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
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).
>
>
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 un
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
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
> defin
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 fo
-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
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/pupp
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
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" n
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
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 wait
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
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
19 matches
Mail list logo