On Tue, Mar 1, 2011 at 5:28 PM, Markus Roberts <[email protected]> wrote: > N -- > >> > That is reassuring. >> > >> > I think if we peel away: >> > >> > * the "always auditing" bug >> >> Yes. I believe this is fixed by Jesse's patch you reviewed: >> >> >> https://github.com/puppetlabs/puppet/commit/e3dfe41ce7da108fc345e58c7df8c1576ea951a0 >> >> > * the "audits notify" surprise >> >> This is a documentation bug. I'll be filing it soon. There's no code >> solution to this, we're not changing behavior. >> >> > * state yaml will "remember" the always audit bug even after it's fixed >> >> As of 2.6.5 + cherry-pick the referenced commit, we do correctly >> overwrite the values in state.yaml > > I think we always "correctly overwrite" the values, but we also notice when > they change. This isn't something that's "been fixed" in a particular > version. > >> >> The undesirable behavior is that this causes an event (which can >> trigger a notify) as you go from :absent to the correct value. > > If :absent is there, I believe it was correct (that is, that the file really > was absent). > > The one case where we have an issue (I believe) is when the file was absent, > being manged but not audited, and we update to a new version with Jesse's > fix at the same time we start auditing. (Without the fix, it's much worse, > as R.I. documented).
all agreed. Thanks for clarifying and tightening the language Markus. I mis-characterized the situation because I was under the impression I'd shown that content changes triggered :absent, not just ... absence. -- 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.
