similar to: Parsechecking in a commit hook

Ok, given the statement on the web page about unlesssystemuser under Resources ( http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources), I assume that users can be purged. However, when I attempt to do this with resources { user: purge => true, noop => true } and what I get is: err: Found a bug: private method ''split'' called for nil:NilClass.

Hi Luke and other people working on 0.24. I hope this is constructive. So, I have our configuration working against a checkout from git as of last night. Subject to (sorry, here''s the big but :) * external_nodes script is not being called (#951) * Custom types aren''t working unless I drop them into $rubysitedir/puppet/{type,provider}. Previously they worked in

After upgrading my puppetmaster server to 0.22.2 using David''s src RPM''s for RHEL4 rebuilt for x86_64 i am getting the following error when puppetd attempts a configuration run. Mon Mar 26 10:05:43 EST 2007 Puppet (err): Could not run Puppet::[1]Network::Client::Master: Invalid value ''nil'' for noop When puppetd is started the initial run is

I don''t manage any macosx machines but I do run puppet standalone to check syntax etc. I''ve been getting the following error: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb": superclass mismatch for class ResourceOverride specifically small test pp files still work, though I''ve found when I use parseonly it

Hello, I was wondering if there is a way to parse individual manifest files as part of a pre-commit hook in subversion. I am looking for something like puppetmasterd --parseonly, but that will work on individual files. This way I can reject a commit if it does not pass. Any ideas? TIA

Hi, I''m testing puppet from the subversion trunk. I have a rather hacked-together system to install a CRM into one of my nodes, which worked (more or less) with version 0.19.3. When I tried to do a puppet run on a completely clean node it seemed to stall on the ''compilation'' part (I do an exec of ''perl Makefile.PL'' in the appropriate dir). When I broke

Hello, I have recently run across the following error: /usr/lib/ruby/1.8/yaml/rubytypes.rb:315: [BUG] Segmentation fault This has happened after adding a particularly large template file with ruby 1.8.1. Thank you, -- Rob -- ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews

Hi everyone, I''m using a svn pre-commit hook to check manifests for syntax errors. I''ve recently upgraded puppet from 0.22.4 to 0.23.2 and the hook stopped working. I use the following command to parse .pp files: /usr/local/bin/puppet --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport /tmp/$$.pp Now, I make a decision based on the exit code. If 0 then commit, else exit

Well imitation is the highest form of flattery they say. So I''m surprised to see these packages neatly built to install into /opt/csw correctly and yet they exist somewhere else and have nothing to do with us here at Blastwave. fascinating. I guess we can always send an email to the person doing this and just ask if they want those packages in testing and then into the catalog for

Hello! I''m trying to use pre-commit SVN hook for checking puppet syntax. For it I try to use some scripts from this thread: http://groups.google.com/group/puppet-users/browse_thread/thread/50ff2eb268f982da?pli=1 But when I try some of the scripts I see the common problem, expression like this: # puppet --parseonly --ignoreimport file.pp produces no output, but "file.pp" has a

os x 10.4.10 used gem to install mongrel 1.0.1. seemed to go w/o errors. "mongrel_rails start -d" spits out this error /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle: Failed to load /usr/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/http11.bundle (LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require''

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

Hi is anybody using the svn pre-commit hook from http://www.reductivelabs.com/trac/puppet/wiki/VersionControlPuppet with 0.24.1 . It was working fine with 0.23.1 and I like it to test stupid typos before checking in. However after updating to 0.24.1 I get the following error for the site.pp: Could not parse for environment development: No file(s) found for import of

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

I read somewhere recently about problems with Puppet and Ruby 1.9. I''m wondering if this is still an issue? Thanks. -- 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

One more error/warning from the latest Puppet from git: In the provider I have KEYS = Facter.value(:roothome) + "/.ssh/authorized_keys" Puppet::Type.type(:authorizedkey).provide(:parsed, ... I get an error on the Puppetmaster: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/provider/authorizedkey/parsed.rb": undefined method `+'' for nil:NilClass Could not

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

What with the impending release and a now fixed bug nagging me, I''m testing puppet [2556] from subversion. There have been changes in packages, I used to have Package { provider => "aptitude", } in my default.pp, but that doesn''t work anymore, and changing package to type or removing the declaration doesn''t help. How do package providers work now?