similar to: --noop ignored: here's why..

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

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

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

Hi All I have a bit of a strange one, and am not sure I''m doing this right. This is with 2.6.4 on Solaris 10 We want to create a sym link from a source file that is created by a package. If the package isn''t installed, puppet in noop is registering an error (big red in the dashboard) because it cannot stat the source file of the link. root@warbjohn# cat /tmp/symlink2.pp

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

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

What is puppet doing here? Nov 17 00:02:01 gumby yum: Installed: tf-starterkit-tfel0-1.0-1.tf.noarch Nov 17 00:02:01 gumby puppetd[720]: (//Node[gumby.fr.xxx.com]/Starterkit::Setup[tfel0]/Package[tf-starterkit-tfel0]/ensure) created Nov 17 00:02:07 gumby yum: Installed: tf-jboss-server-4.2.3.GA-1.tf.noarch Nov 17 00:02:07 gumby puppetd[720]:

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''ve upgraded many of my client machines to version 2.7.10 lately and since on some clients (server is running 2.7.10) i get the following error (running puppetd -tvd --noop --trace): /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `<=>'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181:in `sort'' /usr/lib/ruby/1.8/puppet/simple_graph.rb:181: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

Puppet 2.6.14 is a security release in the 2.6.x branch which addresses CVEs 2012-1053 and 2012-1054. All users of Puppet 2.6.x are encouraged to upgrade when possible to Puppet 2.6.14. Other information available at: http://puppetlabs.com/security or visit http://puppetlabs.com/security/cve/cve-2012-1053 and http://puppetlabs.com/security/cve/cve-2012-1053 Detailed feature release notes are

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

Hi, I''m trying to use Puppet ability to export and collect resources using PuppetDB. My PuppetDB and Puppet Master are running on the same host and I used the PuppetDB puppet module to install PuppetDB and configure the Puppet master. Each time the puppet agent runs on a client, the facts and the catalog are being pushed in PuppetDB and I can query the PuppetDB server to get

I''m trying to manage network files on two nodes, "vico" and "backup." The component "vico_network" below works fine. define vico_network ($owner = ''root'', $group = ''wheel'', $mode = ''644'', $cro_int = ''ne3'', $carp0_skew = '''', $carp1_skew =

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

Hey all- I am trying to set up branch testing as described at http://www.reductivelabs.com/trac/puppet/wiki/BranchTesting , but am running into a few snags. I''ve set up an alternate directory for the testing branch config files, and have created a copy of everything stored under /var/lib/puppet and pointed the test server to that stuff. However, when I try to connect to the test

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

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

I have this ouput when I do a "yum check-update" which is the command which is run in the yumhelper.py : Loaded plugins: rhnplugin, security This system is not registered with RHN. RHN support will be disabled. Skipping security plugin, no data compat-dapl.i386 2.0.13-4.el5 rhel- Server compat-dapl.x86_64 2.0.13-4.el5