similar to: How Does the Interaction Between Facter, Clients, and the Server work

Hello - Is the following a configuration issue (which is usually the case) or a bug? I''m trying to ensure a local user is present in a NIS environment using the following recipie: class dduck_add { user { "dduckl": ensure => present, uid => 60030, gid => "100", groups =>

Greetings - I''ve just started testing Puppet and have a couple of questions: 1. Is there a way to dynamically change a configuraion file that is sent to nodes? For example, I want to modify /etc/hosts to have the hostname and ip address set dynamically - the hosts file shoule look like: 12.34.56.78 node1.example.com 22.35.66.99 server1.example.com But I don''t want to

Can anyone point me to a "Writing Puppet recipes for Dummies" doc? I''m trying to do a basic probe using lspci to see if I have a Qlogic HBA installed on the machine, and if so, install the Qlogic scli package. Here''s a shell script of what I''m trying to do: #!/bin/bash vendor=1077 # QLogic model=2422 # 24xx hba /sbin/lspci -n -d $vendor:$model | grep

I have a custom fact. It syncs correctly, works correctly everywhere when run via ''facter'', and works correctly from puppet on all but one machine. >From ''facter'': # export FACTERLIB=/var/puppet/facts # /opt/puppet/bin/facter itg_location mel But from within puppetd I get: Sep 13 14:54:29 hordac puppetd[768]: [ID 702911 daemon.warning] Could not load fa

Greetings - Maybe I''m a bit slow, but I''ve been trying to understand how to use a module for the better part of a day and I''m not getting it. Here''s what I''ve done: Using puppet 0.23.2 1. Downloaded the shorewall module from David Schmitt''s git repo (Thanks David!!!!) and placed it in the directory /var/lib/puppet/modules (using the rpm

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

Hi, I''m following http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to use a custom fact. My modules looks like: # ls manifests/modules/network/ manifests plugins # ls manifests/modules/network/plugins/facter/primaryint.rb manifests/modules/network/plugins/facter/primaryint.rb as is said in doc. Then: Turn on pluginsync and specify factpath, so that the facts

Hi, On my puppet node, there are many facter variables that are empty in my manifests. But, there are not empty when I start "facter" on the node. why ? ex in a module: class resolver { if $::ipaddress6 { ... } $domainename = "$domain" } In this manifest, $domain and $ipaddress6 are empty In the facter command line, there not empty. -- You received this

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

Is there a repository of Facter plugins that people have made? I''m working on a few that i wouldn''t mind sharing when complete.

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

I''m trying to load custom facts via /etc/facter/facts.d/* according to instructions on http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts I must have missed a setting somewhere because I get nothing. The first clue may be that /etc/facter didn''t exist. I had to create it manually. Is there a setting or search path I need to create? Details: puppet

I''ve just committed Facter 1.3.8. All of the work for this release was done by James Turnbull, so everyone should thank him for getting it done. Here''s the changelog: Fixed Rdoc::usage bug on CentOS 5 - closed Puppet #753 and Facter #40 Added support to return multiple interfaces and their IP addresses and MAC addressess as facts. Returns

If I externalise my Puppet module config to a directory outside of Puppet using the modulepath / manifestdir settings: [main] pluginsync=true modulepath=/home/ec2-user/projects/qmg-puppet/etc/puppet/modules manifestdir=/home/ec2-user/projects/qmg-puppet/etc/puppet/ manifests the agents log the following error: "Could not evaluate: Could not retrieve information from source(s)

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL

Hi I''m trying to add extra facts to facter. The puppetd is running on Debian Etch Amd64 as Xen 3.1 guest. I''ve follow the Wiki on adding the facts. First I used relative path in the manifest and added "factsync=true" in client''s puppetd.conf. And then tested it with "puppetd -vt". But no matter what i tried, this error came: File paths must be fully

Hi, I''ve noticed that defining multiple facts in one file is possible, and puppet can make use of them correctly, but when trying to call with facter --puppet they are not shown, do I need something special to make them work as any other single custom fact? Master is running 2.6.7 This is a custom fact with two facts in it: [modules/foobar/lib/facter/foobar.rb ] require

I installed the 2.6.2 puppet and facter 1.5.8 gems and tried to run puppet, but it failed with the following message: err: Could not run Puppet configuration client: Could not retrieve local facts: uninitialized constant Facter::IPAddress Then I tried running facter alone: # facter /usr/lib64/ruby/vendor_ruby/1.8/facter/ipmess.rb:19: uninitialized constant Facter::IPAddress (NameError) After