On May 20, 4:07 am, tobyriddell <toby.ridd...@gmail.com> wrote: > I realise that the config. for the new host I'm working on doesn't > include the 'nss' class so that would explain why the error appears in > the first place (thanks for helping me track that down). > > But I still don't have a grasp on why it's intermittent...
When the catlog is compiled successfully, does it actually contain the Service['nslcd'] resource? And in that case, does it indeed *not* contain File['/etc/nslcd.conf']? I would be very surprised if both were so, and that would definitely constitute a bug. My guess, however, is that one or more of the following is true: 1) Your node's facts are inconsistent from run to run; this would be surprising for Facter's built-in facts, but it might arise from custom facts you have added. 2) Your manifests use one of the few Puppet features that are evaluation-order dependent. The result could be either that sometimes your "nss" class gets included when you thought it would not be, or that somtimes the class declaring Service['nslcd'] is not included when you thought it would be. 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.
