On Thursday, July 5, 2012 11:26:48 AM UTC-5, Matthew Burgess wrote: > > On Thu, Jul 5, 2012 at 4:56 PM, jcbollinger wrote: > > > Are you sure a Puppet run needs to have already completed before the > facts > > are available from the inventory service? That would be surprising. > Also > > most unfortunate, inasmuch as it implies that the inventory service > would be > > serving stale facts (from a previous run) to your ENC. > > Well, no, to be honest, I'm not sure how the facts are made available > to the ENC/inventory service. > > From what you've written above, I assume the order of events is: > > 1) puppet agent runs > 2) puppet agent gathers facts > 3) puppet agent stores facts in inventory service > 4) puppet server uses facts during compilation and application of the > catalog? > > If that's the case, then all is good, I guess. >
What I know is: 1) The agent performs plugin synchronization, if enabled 2) The agent gathers facts and sends them to the master 3) The master compiles and returns a catalog 4) The agent applies the catalog Recording the facts in the inventory service and running the ENC both happen in step 3. The ENC runs very early, and I don't know for sure whether the inventory is updated first, but the master definitely has the node's then-current facts *somewhere* at that time. If the inventory isn't updated first then I'd consider filing a bug / RFE. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/2sZX6nE20g4J. 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.
