R.I. -- > > 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? >
> so the weird thing for me is these notifies, I cant make them happen again > by deleting state.yaml - after deleting state the first lines reappear but > no notifes get sent. > > I've updated one more machine and could reproduce the same. > What are you updating from? Is it possibly that this is related to the update and not the audit bug...that is, if you update a node to a version with the audit bug fixed, such as the current 2.6.next (HEAD), does it restart the services? -- M ----------------------------------------------------------- When in trouble or in doubt, run in circles, scream and shout. -- 1920's parody of the maritime general prudential rule ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
