>> No good idea yet, but there is something suspicious in your curl >> responses - the "resource" hash, did you obfuscate this yourself on >> purpose? The two hashes between the first and second requests are >> identical. That hash is calculated based on the sum of the resource, >> including parameters - so it seems impossible that PuppetDB arrived at >> the same hash with and without parameters. > > > I think that's just me being too sensorship heavy and abusing copy and > paste, I would have copied some fields from the same example. Trust me that > the resources dictionary was empty though ;-)
So just to clarify, the resources hash '8ba4379c364b9dba9d18836ef52ce5f4f82d0468' was different or the same between the two examples? > Now if I was thinking smart I would have taken a Postgres backup before I > re-freshed all the catalogs, but I didn't, not sure if that would have > helped much. I agree with subsequent posts as well - probably not a > migration problem. It might have helped. Are any other nodes and resources still exhibiting this strange behaviour? Maybe checking for any exported resources with no params might be worthwhile. ken. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
