Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1187447 [details]
Screenshot of the error

Description of problem:
When I try to view a puppet report I get an error instead.

Version-Release number of selected component (if applicable):
6.2.0 GA

How reproducible:
Always

Steps to Reproduce:
1. Have a host managed by satellite with puppet agent configured and failing
2. Go to Puppet reports in Satellite: https://satellite.com/hosts/HOST_FQDN/config_reports
3. Open failed report

Actual results:
Oops, we're sorry but something went wrong no implicit conversion of true into Hash

Expected results:
View of the puppet report on page: https://satellite.com/config_reports/REPORT_NUMBER

Additional info:
The host has the same puppet version as master.

Connecting redmine issue http://projects.theforeman.org/issues/14154 from this bug

Upstream bug assigned to mhulan

Upstream bug component is Reporting

Moving to POST since upstream bug http://projects.theforeman.org/issues/14154 has been closed

this has not been merged yet, your configuration report does not include the relevant condition (it requires the time in which the report was created vs the time in which the report was accepted - usually indicating a time / clock drift).

Verified in Satellite 6.2 Snap 1.2

Followed same steps as above, but used puppetlabs/ntp module to stop autosync with ntp server. Then remote execution to adjust the system time a day forward. Page then shows an error that the host seems to be adrift. See attached.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1615