similar to: Flag to not apply changes

So I am beginning the long process of learning puppet... and it seems that I am missing some vital things. My systems are RHEL-4, and i have installed the puppet/facter/puppetmasterd from dlutter@redhat.com''s archive. [root@canopus puppet]# rpm -qa | egrep ''puppet|facter'' | sort facter-1.3.6-1.el4 puppet-0.22.2-1.el4 puppet-server-0.22.2-1.el4 on the client I

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

I want to use puppetrun so I added --listen to the puppetd command-line. Puppetd would run and then immediately exit. I couldn''t figure out the cause because there was nothing in the logs. I finally figured it out when I ran it with --verbose. # puppetd --listen --verbose Will not start without authorization file /etc/puppet/namespaceauth.conf My guess is that the fatal message is

Hello, I have two Vmware images, with 256MB of RAM memory each one, running puppetmasterd for the server and puppetd for the client. It''s normal that my puppetmasterd and puppetd occupies almost 10% of RAM memory each one? They aren''t doing anything especial, just listening on the ports. Thanks.

How are people upgrading puppet itself on their hosts that run puppetd? Can puppet be used to upgrade to a new puppet package via gem, rpm or some other package provider? How do you handle restarting? Just hoping theres a better way than "ssh and a for loop" or having to have another configuration management system installed.

I am writing a definition that installs a crontab. I would like it to run the command only when the downloaded file changes. I am using "subscribe" but it doesn''t seem to do the job. The exec command is run every time. define crontab($host = $hostname) { $path = "/tmp/$name.$host.cron" remotefile { $path: source =>

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi All, I was surprised to notice that a call to noop from puppetrun did not work as expected. on the agent side (for this case the server side..), I ran: puppetd --verbose --no-daemonize (where listen is set in the puppet.conf) on the puppet server side(in this case the client side), I ran: puppetrun --noop --host SERVER notice: SERVER(IP) triggered run info: Caching catalog at

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hi, I am looking for a way, i.e. best practice for managing config changes safely and efficiently. Something like clever module organization could certainly help, but I am looking for something else as well: Is it possible to set up puppetd in a way, that it just listens and reports, but does not apply config changes automatically, and in the same time has the ability to trigger it somehow?

Greetings. Long story short ... configuration changes were made to my puppet clients while my puppet server was unavailable. I would like to run puppetd in such a way that it will list what files it would replace, but not actually replace them, so that I can synchronize my server with my various clients. rsync has a -n (--dry-run) option that does this. But I can''t find one in

Hi, I can''t find an option of the puppetd client that can just print what the puppetd client will do on my system (updateing files, installing softwares, etc), but without doing all the things (like a "diff" between the current state of my system and the state defined on the puppet server). Is such option exists ? Regards

Hello. I''m a long time cfengine user, some might say sufferer, and I have finally managed to get around to experimenting with Puppet. So far I''m very impressed. I am trying to get puppet to configure the openntpd config file, from an ERB template, based on the node definition in the site config. What I''m trying to understand is why when I define a variable in a child

Trying to setup a sandbox environment, and I''m running into some issues. When I run the system in --noop mode, everything works as it should (long list of options truncated to ...): [root@kvm001 ~]# puppetd ... --noop info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //dev_server/basenode/role_general/ntpd/File[/etc/localtime]/ensure: is

Hello I often configure a new node that I want to be the same as an existing one. However I''d like to run puppetd with --noop just the once to double check the changes (I''m still responsible for them after all) Trouble is on a new node the keys etc aren''t there and running as noop they don''t get made and I get nowhere. Unless someone knows a different way to

Hello all, I''m thinking about a configuration class that, amongst other things execs out to a ''dangerous'' configuration script. I''d like to make this a noop by default, so the operator has to try a bit harder to invoke it. So I thought about doing something like: class blah { exec { danger: noop => true, tag => hitme, command

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

Hi, I have Redhat 9 & RHEL 4.2 with puppet clients installed. When is use puppetd -test the updates get effected, but when when running them as daemon mode nothing happens. ## Nothing Happens - no change is detected /etc/init.d/puppet status puppetd (pid 15538) is running... ## When running manually puppetd -test the changes from server gets updated. Is there any

I''m thinking about how to set up the processes for Production puppet runs now. Being ultra-conservative here, we''d like to see what would happen before pressing the red button. I can run in noop mode, and everything is evaluated but nothing is done. A YAML report magically appears on the Puppetmaster which my script parses and spits out something the management can read

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