Goodday I have a small puppet install with 3 servers currently, two Centos 5.2, one RedHat 5.0...
I recently added the RedHat 5.0 to puppet management, and did the run with a --noop to verify what would happen without touching the box. The box was (violently ;-) updated anyway. That is to say the --noop was a "noop" all changes were applied. All servers have the packages from epel: puppet-0.24.6-1.el5 facter-1.5.2-2.el5 All servers have ruby 1.8.5. The reason for the discrepancy appears to be that the working servers have a /etc/puppet/puppet.conf with a '[main]' section, whereas the server which wouldn't --noop had an /etc/puppt/puppetd.conf with a (corresponding) '[puppet]' section as a legacy from the upgrade from an older dag repo version to the epel version. Needless to say it was very surprising to apply changes to the server for what turned out to be a deprecated config file setup which gave no warning of this (potentially catastrophic) side-effect of not honouring --noop. Some kind of warning or error would be far more appropriate than silently ignoring the --noop for whatever reason. Regards -ant --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
