I'm running puppet 4.1.0 in a test VM in preparation for an eventual migration from 3.8.1. I've recently run into an issue that seems to be mentioned in https://tickets.puppetlabs.com/browse/PDB-949
Here's a little back info; My VM is a copy of our production puppet master, but with 4.1.0 and puppetserver 2.1.0 installed. It is using the same production puppetdb. With both the production and virtual puppet masters talking to the same puppetdb, it became vary obvious that the 4.1.0 puppet master was using cached fact data from puppetdb to compile a catalog, yet still saving the new facts in puppetdb. To help with the eventual transition, I have a couple areas in the manifests that check the $::puppetversion. When using the cached facts from puppetdb, it would compile the catalog as if puppet 3.8.1 had made the request, then it would fail on the next run because it would request pull in the "trusted" fact from puppetdb and error 400 on me. If I disable "storeconfigs", then everything works properly (minus saving the info in puppetdb). This ticket seems to be about this issue, but it doesn't show much activity: https://tickets.puppetlabs.com/browse/PUP-3438 Is there any other way to work around this critical error other than setting "storeconfigs" to "false"? -- 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/a84107b0-c669-493f-9569-a34b95389cfb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
