On Wednesday, November 28, 2018 at 6:32:44 PM UTC, Eric Sorenson wrote: > > Hi Darragh, the fact that the error message contains a '400' error > suggests the problem happens on the server when it receives the report. > > My first guess given that error message is also that there's a mix of > versions installed, but it's weird that it only happens on some reports. > Maybe there is something malformed in those reports that triggers a > different code path on the server. >
Indeed there is, I missed that there were errors further back in the output log previously and assumed the failure to post the report successfully was the error. Seems they are not compilation errors but rather runtime errors where something unexpected occurred in applying the catalog. For successful runs there is no problem in posting back the report, this at least now gives me something to reproduce consistently, just add an error somewhere that will trigger it. > You can save a copy of the reports by adding `store` to the type of report > submission on the master: `reports = https,store` and see what they look > like. They should go into a subdirectory > of /opt/puppetlabs/puppet/cache/reports > > HTH > --eric0 > Ah, fantastic, didn't think of that! That will definitely help, many thanks. With spotting why it was occurring this will hopefully help me track down the cause. Fortunately now that I've discovered it's not the cause of the failures but a side effect, it's definitely less worrying, but still odd that it occurs. -- Darragh Bailey -- 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/9314c94e-189a-42ed-92bf-c70eda3b9c55%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
