R.I.Pienaar wrote:
I just updated one machine and it seems auditing is enabled by default:Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/mode) audit change: newly-recorded value 444 Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/type) audit change: previously recorded value absent has bee n changed to file Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/owner) audit change: newly-recorded value 0 Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/group) audit change: newly-recorded value 0 Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/content) audit change: newly-recorded value {md5}a6e2bd8b1af 51c376c44c9aeb7401a89 Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/File[/etc/mcollective/policies/default.policy]/ensure) audit change: newly-recorded value file Worse it seems changing auditing sends notifies: Mar 1 08:55:57 monitor2 puppet-agent[9797]: (/Stage[main]/Mcollective::Config/File[/etc/mcollective/policies/]) Scheduling refresh of Service[mcollective] Mar 1 08:56:01 monitor2 puppet-agent[9797]: (/Stage[main]/Mcollective::Service/Service[mcollective]) Triggered 'refresh' from 13 events Zero manifest changes, just updating to new Puppet == all services with notify/subscribe restart. Can someone else confirm they saw this behavior before I file a ticket?
RI There's already a ticket: http://projects.puppetlabs.com/issues/6443 A regression was missed. We're working on it now. James -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
