Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1189

Custom reports not working (Class is already defined in Puppet::Reports)

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.3.0
    • Component/s: Modules
    • Labels:
    • Template:
    • Story Points:
      0
    • Sprint:
      Client 2015-12-02
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Previously, if a report handler failed during initialization, it wasn't
      cleaned up. So the second time a report was submitted, Puppet would try
      to instantiate a new class, and then fail because it had already been
      instantiated. This instructs the class loader to overwrite if needed.
      Show
      Previously, if a report handler failed during initialization, it wasn't cleaned up. So the second time a report was submitted, Puppet would try to instantiate a new class, and then fail because it had already been instantiated. This instructs the class loader to overwrite if needed.

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              redmine.exporter redmine.exporter
              QA Contact:
              Kurt Wall
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support