Puppet users - Aug 2008 - More than likely a simple fact-distribution question.

I''m clearly failing to understand the way puppet and ruby work, but I
now
can''t see the wood for the trees, so...

... I''m trying to emit a custom fact; raidstate.rb, that resides in
/var/puppet/facter

The config files look like this:

zaphod:/etc/puppet jhr$ cat fileserver.conf
[module]
path /var/puppet/clientbucket/banjax
allow *.mysparedomain.com

[facts]
path /var/puppet/facter


zaphod:/etc/puppet jhr$ cat puppet.conf
[main]
pluginsync = true
factpath = /var/puppet/facter


... Which appears to do the right thing, or at least not complain, when I
run puppet -v on the server. However, on the sacrificial client we see this:


jhr$ sudo puppetd -vt --factsync --server puppet.mysparedomain.com
info: Retrieving facts
err: /File[/var/puppet/facts]: Failed to generate additional resources
during transaction: Cannot access mount[facts]
err: /File[/var/puppet/facts]/source: Could not describe /facts: Cannot
access mount[facts]
warning: /File[/var/puppet/facts]/ensure: No specified sources exist
notice: Ignoring cache
info: Caching catalog at /var/puppet/state/localconfig.yaml
notice: Starting catalog run
notice: Finished catalog run in 0.30 seconds


--
John Hawkes-Reed
Systems Administrator. Future Publishing. x 2526


--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Wed, 2008-08-06 at 14:02 +0100, John Hawkes-Reed
wrote:
> >snip<
> [facts]
> path /var/puppet/facter
> 
> 
> zaphod:/etc/puppet jhr$ cat puppet.conf
> [main]
> pluginsync = true
> factpath = /var/puppet/facter
> >snip<
> err: /File[/var/puppet/facts]: Failed to generate additional resources
> during transaction: Cannot access mount[facts]
> err: /File[/var/puppet/facts]/source: Could not describe /facts: Cannot
> access mount[facts]
I''d say that you don''t have any "allow" directives
for the fact mount.
It is my understanding that factsync are deprecated with puppet >0.24.x and
you should use pluginsync instead:
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules

-- 
Brice Figureau <brice-puppet@daysofwonder.com>


--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 6/8/08 14:19, "Brice Figureau"
<brice-puppet@daysofwonder.com> wrote:
>
>
> On Wed, 2008-08-06 at 14:02 +0100, John Hawkes-Reed wrote:
>>> snip<
>> [facts]
>> path /var/puppet/facter
>>
>>
>> zaphod:/etc/puppet jhr$ cat puppet.conf
>> [main]
>> pluginsync = true
>> factpath = /var/puppet/facter
>>> snip<
>> err: /File[/var/puppet/facts]: Failed to generate additional resources
>> during transaction: Cannot access mount[facts]
>> err: /File[/var/puppet/facts]/source: Could not describe /facts: Cannot
>> access mount[facts]
>
> I''d say that you don''t have any "allow"
directives for the fact mount.
Yes. That was it. Thank you.
> It is my understanding that factsync are deprecated with puppet >>
0.24.x and you should use pluginsync instead:
> http://reductivelabs.com/trac/puppet/wiki/PluginsInModules
That''s my understanding, too. However, that page is making my brain
hurt, so
I suspect I need to take a step back and get more of a clue about Ruby
first.

--
John Hawkes-Reed
Systems Administrator. Future Publishing. x 2526


--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Puppet actually has its own configuration language but is written in
Ruby.  So if you are writing puppet code, Ruby knowledge isn''t
actually a necessity (except maybe for templates and that only very
rudimentary).  However if you are writing puppet source code (ie- to
submit a patch) then Ruby knowledge will help you out greatly.

On Aug 6, 6:54 am, John Hawkes-Reed <John.Hawkes-R...@futurenet.com>
wrote:
> On 6/8/08 14:19, "Brice Figureau"
<brice-pup...@daysofwonder.com> wrote:
> > On Wed, 2008-08-06 at 14:02 +0100, John Hawkes-Reed wrote:
> >>> snip<
> >> [facts]
> >> path /var/puppet/facter
>
> >> zaphod:/etc/puppet jhr$ cat puppet.conf
> >> [main]
> >> pluginsync = true
> >> factpath = /var/puppet/facter
> >>> snip<
> >> err: /File[/var/puppet/facts]: Failed to generate additional
resources
> >> during transaction: Cannot access mount[facts]
> >> err: /File[/var/puppet/facts]/source: Could not describe /facts:
Cannot
> >> access mount[facts]
>
> > I''d say that you don''t have any "allow"
directives for the fact mount.
>
> Yes. That was it. Thank you.
>
> > It is my understanding that factsync are deprecated with puppet
>> > 0.24.x and you should use pluginsync instead:
> >http://reductivelabs.com/trac/puppet/wiki/PluginsInModules
>
> That''s my understanding, too. However, that page is making my
brain hurt, so
> I suspect I need to take a step back and get more of a clue about Ruby
> first.
>
> --
> John Hawkes-Reed
> Systems Administrator. Future Publishing. x 2526
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---