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 /var/lib/puppet-agent//localconfig.yaml notice: Starting catalog run notice: //Node[SERVER]/test/Exec[echo "This is the Test Class"]/returns: executed successfully notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: Filebucketed to main with sum fe274facc165e952f32848c8798306a9 notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/content: content changed ''{md5}fe274facc165e952f32848c8798306a9'' to ''{md5}dcab80e2b06f2e7bded875a7efd5cea6'' info: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: Scheduling refresh of Service[puppet] notice: //Node[SERVER]/base/puppet/Service[puppet]: Triggering ''refresh'' from 1 dependencies notice: Caught TERM; shutting down notice: Shutting down Killed (as a sidenote, puppetd dies in this case) So, the question is, where exactly is the noop option valid? puppetd command line puppetd conf from any resource object? can it be set anywhere on the puppetmasterd settings? Here is the use case that I am working with. I would like to be able to run all puppet agents in noop mode when there is new puppet code deployed. I would like to this action to be controlled from a central location. Any suggestions are appreciated. regards, Dan --~--~---------~--~----~------------~-------~--~----~ 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
---------- Forwarded message ---------- From: Dan Bode <bodepd@gmail.com> Date: Fri, Jul 10, 2009 at 3:49 PM Subject: using noops from puppetrun To: puppet-users@googlegroups.com 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 /var/lib/puppet-agent//localconfig.yaml notice: Starting catalog run notice: //Node[SERVER]/test/Exec[echo "This is the Test Class"]/returns: executed successfully notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: Filebucketed to main with sum fe274facc165e952f32848c8798306a9 notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/content: content changed ''{md5}fe274facc165e952f32848c8798306a9'' to ''{md5}dcab80e2b06f2e7bded875a7efd5cea6'' info: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: Scheduling refresh of Service[puppet] notice: //Node[SERVER]/base/puppet/Service[puppet]: Triggering ''refresh'' from 1 dependencies notice: Caught TERM; shutting down notice: Shutting down Killed (as a sidenote, puppetd dies in this case) So, the question is, where exactly is the noop option valid? puppetd command line puppetd conf from any resource object? can it be set anywhere on the puppetmasterd settings? Here is the use case that I am working with. I would like to be able to run all puppet agents in noop mode when there is new puppet code deployed. I would like to this action to be controlled from a central location. Any suggestions are appreciated. regards, Dan --~--~---------~--~----~------------~-------~--~----~ 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Dan Bode wrote:> 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 /var/lib/puppet-agent//localconfig.yaml > notice: Starting catalog run > notice: //Node[SERVER]/test/Exec[echo "This is the Test Class"]/returns: > executed successfully > notice: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: > Filebucketed to main with sum fe274facc165e952f32848c8798306a9 > notice: > //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]/content: > content changed ''{md5}fe274facc165e952f32848c8798306a9'' to > ''{md5}dcab80e2b06f2e7bded875a7efd5cea6'' > info: //Node[SERVER]/base/puppet/File[/etc/puppet/puppet.conf]: > Scheduling refresh of Service[puppet] > notice: //Node[SERVER]/base/puppet/Service[puppet]: Triggering ''refresh'' > from 1 dependencies > notice: Caught TERM; shutting down > notice: Shutting down > Killed (as a sidenote, puppetd dies in this case) > > So, the question is, where exactly is the noop option valid? > puppetd command line > puppetd conf > from any resource object? > can it be set anywhere on the puppetmasterd settings? > > Here is the use case that I am working with. I would like to be able to > run all puppet agents in noop mode when there is new puppet code > deployed. I would like to this action to be controlled from a central > location. Any suggestions are appreciated.I''ve found http://projects.reductivelabs.com/issues/864 from a year ago, which requests exactly being able to specify noop yes/no via puppetrun. Sadly, it is still open. Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---