Actually, I've just re-read your message. I don't think we're talking about quite the same thing.
It's not that the end results are non-deterministic, but rather that Puppet occasionally bleats about missing dependencies. So it's the error-reporting that's non-deterministic. On May 19, 3:04 pm, tobyriddell <toby.ridd...@gmail.com> wrote: > Thanks for the explanation - nice to know there's a good reason for > it. > > On May 19, 2:01 pm, jcbollinger <john.bollin...@stjude.org> wrote: > > > On May 19, 2:23 am, tobyriddell <toby.ridd...@gmail.com> wrote: > > > > I've got a bit of a strange one here. I'm seeing intermittent errors > > > for missing resource dependencies. > > [...] > > > it's just that I'd expect the errors to be present the entire time > > > rather than intermittent. > > > Prior to version 2.7, the relative order in which Puppet attempts to > > apply resources that have no dependency relationship is non- > > deterministic. Some would consider that a feature (missing > > dependencies will eventually be detected), but project leadership has > > decided that runtime consistency is more valuable, so that is > > implemented for 2.7. If the root problem is solely missing > > dependencies in your manifests, then the behavior you describe is > > completely normal for Puppet 2.6.x and earlier. > > > John > > -- 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.
