similar to: testing with fake facts

Hello I am entertaining the idea of putting some time and effort into making Facter and Puppet run on MS Windows. Call me crazy ... Does anyone know anything about the issues that I''m likely to face? What are the major stumbling blocks? Initially I''d be happy just getting File to work, this would be of tremendous value. I''m guessing that Facter will require the

Hello I am thinking that it is better to do a cvs export of a project once, on the puppetmaster box, rather than do the same cvs export on all puppet clients, yes? If so, how does one do this? Do you run puppetd on the same box as puppetmasterd and set up the cvs export as an exec for only the node with the same hostname as the puppetmaster? Thanks Jesse Jesse Reynolds Virtual

fact loads: I use facter to search the rsync path and then i write this sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath",

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

Here at the University of Sydney I''m trying to give Puppet a go. I haven''t made it past first base yet unfortunately. We run RHEL 4 here, for the most part, and the install guide at http://reductivelabs.com/trac/puppet/wiki/InstallationGuide says that you should use the vendor''s Ruby, but Red Hat''s current version of Ruby is 1.8.1-07 - is this new

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

Hi. When running "puppetd --server <puppetmaster> --waitforcert 50 --test" on a puppet client we get the following error: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect''

Hi, The following is with the latest (and last) puppetmaster/puppetd on FC5. I use puppet to configure a server and several workstations on my home network. This includes managing several files of >5Mbyte on the workstations. I have had problems recently with timeout errors on some of these files. These errors seem consistent for a particular puppet setup/configuration, but can change when

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

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

Hello I have a puppetmasterd installation running on a Mac OS X 10.6.3 Server with puppet installed via macports. Earlier today it was happily signing requests, before I upgraded puppet from 0.24.8 to 0.25.4. Now I get "Invalid argument": bash-3.2# puppetca --sign bouti.carbonplanet.com bouti.carbonplanet.com err: Could not call sign: Invalid argument The only mention I can find on

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to

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

err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

I have a test area network that is not routed to the production network because of IP address space re-use between the two networks. I would like the puppetmaster to serve both the production and test area networks. The puppetmaster is on the production network. I understand the puppet to puppetmaster connect to be HTTP using SSL. Can I somehow setup the puppet clients to use an HTTP

Hello, all. I am getting the following error on a couple of my puppet nodes when I run puppetd -v -o --no-daemonize --no-splay: err: Could not retrieve catalog: undefined method `-'' for #<XMLRPC::DateTime:0xb7c729e8> The error goes away if I add --ignorecache, but I''m not sure that''s quite the fix I''m hoping for. It will also go away if i remove my

Hi. I''d like to use exception handling in my custom facts. For example, in plain Ruby: begin buildno = '''' bcrelease = open("/etc/BCrelease") while (line = bcrelease.gets) line = line.chomp buildno = $1 if line =~ /^Build:\s+(\d+)/ end bcrelease.close print "#{buildno}\n" rescue print "No

Hi, I''m new to puppet and having difficultly setting it up the way I want to (which is a little different from the norm I''d say). What I''m trying to achieve is to have a automatic build of debian (etch at the moment) using debian installer that installs a minimal system including puppet using the debian package puppet (not puppetmaster). As part of the initial setup