Issue #17883 has been updated by eric sorenson. Status changed from Unreviewed to Investigating Assignee set to eric sorenson
I am having trouble reproducing this locally -- it's working under 2.7.20 and 3.0.2 w/ the boundary report processor. I noticed a comment on the README.md for datadog_reports that seemed promising: <pre> If you get err: Could not send report: Error 400 on SERVER: Could not autoload datadog_reports: Class Datadog_reports is already defined in Puppet::Reports Make sure reports=datadog_reports is defined in [master], not [main]. <pre> But moving my reports directive up to the `[main]` section did not cause an issue for me. ---------------------------------------- Bug #17883: Custom reports not working (Class is already defined in Puppet::Reports) https://projects.puppetlabs.com/issues/17883#change-77891 Author: Scott Smith Status: Investigating Priority: Normal Assignee: eric sorenson Category: Target version: Affected Puppet version: 2.7.20 Keywords: Branch: I've got a client experiencing this with the boundary report from https://github.com/puppetlabs/puppetlabs-boundary Also someone in #puppet said they get it with the datadog report in Puppet 3.0. Here's the full message we get at the end of the run: err: Could not send report: Error 400 on SERVER: Could not autoload boundary: Class Boundary is already defined in Puppet::Reports -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
