Ken, Kevin, good evening. On Thu, 23 Jul 2015 17:58:20 +0100 Ken Barber <k...@puppetlabs.com> wrote:
> The problem is, that if you're contacting PuppetDB in this case for > your fact information, something is wrong. The 'bug' is that if PDB is > referenced for this information it tries to clobber trusted_facts, but > you should never get this far under a compilation workflow. > > This can sometimes be caused by a timing issue, due to the cache > looking like its expired (even though it was just written) so it > reaches out to the PDB terminus for its answer. Kevin also suggested skew could cause this but I can rule that out as the master was failing on itself. > The other cause can be a misconfigured routes.yaml, or some other > workflow problem. What does your routes.yaml look like? This can be > misconfigured to always use PDB for that information, which is bad. > Facts should come from agents, not from a cache inside PDB during > compilation :-). BINGO I had no routes.yaml (the 3.8.1 yaml was in the wrong place in the move not only in software but to environments too). Putting that back into $confdir and with a puppetserver restart all is well again. Thanks both for your time and help. Cheers, Steph -- Steph Gosling <st...@chuci.org> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150723231132.085da2c69cbbf44cf9b75385%40chuci.org. For more options, visit https://groups.google.com/d/optout.
