> A lot of the time you can get away with just a shell provider and type
> for manifest validation, as the client will get the right one synced
> down for use in actual resource application.
Is an appropriately named but empty type/provider in the default
environment adequate to fool puppetmaster?
> You didn't read the bit (which, IIRC, isn't all that obvious) that explains
> that custom types and plugins don't play very nicely with environments;
Yep. I missed that.
> I think the developers just committed a fix for that to a branch, ready for
> testing, so you might want to troll the BTS
On Fri, Jun 11, 2010 at 7:59 PM, Daniel Pittman wrote:
> Ben Beuchler writes:
>
>> I found myself unable to load/use a custom type I've been working on. To
>> minimize the variables, I copy-n-pasted the "File" example from the
>> documentation link below, just changing the name from "file" to "h
Ben Beuchler writes:
> I found myself unable to load/use a custom type I've been working on. To
> minimize the variables, I copy-n-pasted the "File" example from the
> documentation link below, just changing the name from "file" to "haddock" to
> avoid conflicting with the real File type.
[...]
I found myself unable to load/use a custom type I've been working on.
To minimize the variables, I copy-n-pasted the "File" example from the
documentation link below, just changing the name from "file" to
"haddock" to avoid conflicting with the real File type.
http://projects.puppetlabs.com/p
Eric Gerlach wrote:
> On Fri, May 28, 2010 at 09:44:59PM +1000, James Turnbull wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Paul Lathrop wrote:
>>> Haha!
>>>
>>> So much for my purchase of puppetstrings.net! I guess I can scrap the
>>> crappy code I had put together, too. :-P
>>
On the client, what is the output if you do
puppetd --test --debug
~Charles~
On Fri, Jun 11, 2010 at 2:18 PM, jg wrote:
> (puppet 0.25.4)
>
> I make the client request for a certificate:
>
>$ puppetd -t --waitforcert 30
>
> And expect the ca server to have the client's FQDN listed:
>
>
On Thu, Jun 10, 2010 at 02:55:04PM -0700, Nigel Kersten wrote:
>On Thu, Jun 10, 2010 at 12:53 PM, <[1]tean...@gmail.com> wrote:
>
> I have my sudoers setup as per the puppet training class recommendation:
>
> � � � �file { "/etc/sudoers.check":
> � � � � � � � �content => templ
On Fri, May 28, 2010 at 09:44:59PM +1000, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Paul Lathrop wrote:
> > Haha!
> >
> > So much for my purchase of puppetstrings.net! I guess I can scrap the
> > crappy code I had put together, too. :-P
>
> Well if you have feat
(puppet 0.25.4)
I make the client request for a certificate:
$ puppetd -t --waitforcert 30
And expect the ca server to have the client's FQDN listed:
$ puppetca --list
[none listed]
There's also nothing under the certificate_requests directory:
$ ls /var/lib/pu
Thomas I don't see your GIT repo, looks to be offline.
On Fri, May 14, 2010 at 5:11 AM, Dan Carley wrote:
> On 12 May 2010 16:13, Thomas Bellman wrote:
>
>> [..]
>> I don't create the logical volumes automatically, nor do I
>> partition or create filesystems on them automatically, to lessen
>>
On 06/09/2010 04:57 AM, Klaus Ethgen wrote:
Exact. And I still read that sources. With the Sshkey type there is
still a implemented solution to collect that keys and export them to all
hosts. But that Type only allow to export one of the two hostkeys a host
have. And that is the source of my que
kit wrote:
> I'm getting this error message quite often on the puppet clients. I
> don't know what it means. Restarting puppet often helps and the
> messages will go away, but suddenly it will come back again. Any
> thoughts?
>
What Puppet, Ruby versions and platform would help too please!
Thank
Great, it works like a charm.
Cheers,
Henry
On Jun 11, 11:50 am, Nigel Kersten wrote:
> On Fri, Jun 11, 2010 at 8:47 AM, CraftyTech wrote:
> > Hello All,
>
> > newbie question here:
> > So I have:
> > /etc/puppet/modules/foo
> > /etc/puppet/modules/foo/manifests/init.pp
> > /etc/puppet
On Fri, Jun 11, 2010 at 8:47 AM, CraftyTech wrote:
> Hello All,
>
> newbie question here:
> So I have:
> /etc/puppet/modules/foo
> /etc/puppet/modules/foo/manifests/init.pp
> /etc/puppet/modules/foo/manifests/something.pp
>
> something.pp: class something{}
> init.pp: class foo {
>
Hello All,
newbie question here:
So I have:
/etc/puppet/modules/foo
/etc/puppet/modules/foo/manifests/init.pp
/etc/puppet/modules/foo/manifests/something.pp
something.pp: class something{}
init.pp: class foo {
include foo::something
{}
}
For some reason,
> I'm getting this error message quite often on the puppet clients. I
> don't know what it means. Restarting puppet often helps and the
> messages will go away, but suddenly it will come back again. Any
> thoughts?
This a ruby error. Could you run puppetd with the "--trace" option ?
This should p
I'm getting this error message quite often on the puppet clients. I
don't know what it means. Restarting puppet often helps and the
messages will go away, but suddenly it will come back again. Any
thoughts?
--
You received this message because you are subscribed to the Google Groups
"Puppet User
18 matches
Mail list logo
