similar to: parsing manifests in a pre-commit hook

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

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

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override

hello,all. Is there a have some tools to check the puppet manifests before to use it ? like nagios -v nagios.cfg .the new version puppet client can''t get error syntax message,so ,when have some syntax error I can''t found it. -- Huang Mingyou

Hi there, I''m running puppetmasterd manually while testing, and I was trying to split my manifest in several parts using import. If I do so whenever I run the puppetmasterd the manifest gets loaded and served correctly: cognos ~ # puppetmasterd -v info: Starting server for Puppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org

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

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

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

I''m running into a very odd occurrence. I started with a new puppet server and was able to add a few classes, however as I try and add new ones I get odd parsing error messages, the most common being Could not match ''}'' at whatever file. Here is the exact error I get err: Could not retrieve catalog: Could not parse for environment production: Could not match

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 As I''m more familiar with cfengine and it''s way to split updates (in update.conf) from the actual grunt work (in cfagent.conf), I''m wondering how to best manage puppet and my manifests with puppet...? Should I define a puppet class that copy the puppet package (in .tgz format) and all the manifests to the client, and then have all my other classes depend on

We have started having developers make changes to our manifests file. We have a couple of changes with errors that have broken updating for all clients. We even ran into a bug where a broken configuration on puppetmaster start would cause it to return 500 server errors to all clients. I would like to have a way for developers to check their changes before committing them to version control and

Hi, I am sure this subject has come up before. I did not find anything on Google that comes close to what I am trying to do. I would like to manage different groups on multiple nodes using puppet and do not know of a good way to do it. Does anyone have an idea of how I can accomplish this? Any help will be appreciated. Thanks, Mouncef _______________________________________________

I restarted puppetmasterd and it announced that the Cert does not match existing key ! [root@puppet ~]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.1 info: mount[files]: allowing 10.100.0.0/16 access info: mount[files]: allowing *.gridapp.com access info: mount[files]: allowing *.dev.gridapp.com access info: Retrieving existing certificate for

Is there any "correct" way to get puppetmasterd to not spam syslog with (mount[blah]) File source foo does not exist messages when using file source selection lists? I use them quite extensively, so it''s getting quite out of hand. The last resort will be to comment out the offending print statement! -- Russell A. Jackson <raj@csub.edu> Network Analyst California State

Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password

Hi all, This has theoretically been a high priority for a long time, and I''m finally going to get it done, I think. Here''s my plan, and I''d appreciate any comments you might have on it. Currently, sections only have meaning internally, in that one can call ''config.use(section)'' to create any directories needed for that section. Additionally,

Hello, i wanted to know if we can use exported ressrouces to do things like this: - for all nodes tagged as xxx create on the node yyy a file which content is a template where we can have each hostname , or create one file per nodes matching exemple /etc/hosts.allow sshd: host1 sshd: host2 ... or /etc/backuppc/host1 /etc/backuppc/host2 ... from the docs it seems i can collect only ALL

After reading the rc.subr(8) man page and Newburns''s article on the rc.d subsystem[1], It''s clear that a rc.conf.d per service file structure is already natively supported on FreeBSD. I''ve verified this with my own testing: # echo puppetmasterd_enable=\"YES\" > /etc/rc.conf.d/puppetmasterd # /usr/local/etc/rc.d/puppetmasterd start Performing sanity check