If I remove the extension .rb the facter dosen't work. So that's not the
issue.
/Patrik
--
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 em
On 05/18/2011 05:18 PM, Patrick wrote:
>
> On May 18, 2011, at 1:20 AM, patant wrote:
>
>> Good idea!
>>
>>
>> Now I found another problem.
>> Some facts dosent't works when I call them explicit.
>>
>> The facter shows up in the list when I run facter --puppet.
>> But when I call facter --puppet
On May 18, 2011, at 1:20 AM, patant wrote:
> Good idea!
>
>
> Now I found another problem.
> Some facts dosent't works when I call them explicit.
>
> The facter shows up in the list when I run facter --puppet.
> But when I call facter --puppet it dosen't give me the value
> that I got in the
Good idea!
Now I found another problem.
Some facts dosent't works when I call them explicit.
The facter shows up in the list when I run facter --puppet.
But when I call facter --puppet it dosen't give me the value
that I got in the list. Returns nothing.
"facter" gives me:
--
uptime
I extend this a bit in some of my facts to check that the gem is available
before using it. That way if the gem can't be loaded (normally because it
isn't installed), it will still return a value that I can use in the
manifests.
Facter.add("ibmim_installed_version") do
setcode do
ibmim
Found the error:
require 'rubygems'
require 'mygem'
Facter.add("myfacter") do
setcode do
--
This works:
Facter.add("myfacter") do
require 'rubygems'
require 'mygem'
setcode do
---
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
T
require 'rubygems'
require 'yourgemname'
That should be enough. You're going to have to start giving more info
you want more help. At the very least the gem name. Sometimes you
think you're requiring the gem correctly based on the gem name, but
the thing you need to require might not match the
I do require rubygems.
--
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
The gem is installed on the clients and the facter works on the client. It's
when I do the puppet apply/run I get the error.
--
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
On 05/13/2011 07:55 AM, Patrick wrote:
Facter is run on the clients. Does installing that gem on the clients
fix the error?
Also, "require 'rubygems'" on the top of the file where you define your
facter.
--
Pietro Monteiro
Senior Developer
DECK Monitoring
115 W 8th Ave. Eugene, Oregon 9740
On May 13, 2011, at 7:05 AM, patant wrote:
> Hi,
>
> Created a facter that require a gem. The gem is installed on all the servers
> involved.
> But when I trigger puppet I get an error in the log:
> Could not run Puppet configuration client: Could not retrieve local facts: no
> such file to lo
Hi,
Created a facter that require a gem. The gem is installed on all the servers
involved.
But when I trigger puppet I get an error in the log:
Could not run Puppet configuration client: Could not retrieve local facts:
no such file to load --
Is there a way to make puppet use/find the gem?
Us
12 matches
Mail list logo
