Bug 1364049

Summary: Puppet report page shows error
Product: Red Hat Satellite Reporter: Alexander Braverman <abraverm>
Component: ReportingAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bkearney, cwelton, jcallaha, ohadlevy
Target Milestone: UnspecifiedKeywords: Regression
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14154
Whiteboard:
Fixed In Version: foreman-1.11.0.51-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-16 07:11:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of the error none

Description Alexander Braverman 2016-08-04 11:38:02 UTC 
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.
Comment 1 Ohad Levy 2016-08-04 11:39:18 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/14154 from this bug
Comment 3 Bryan Kearney 2016-08-04 14:17:16 UTC 
Upstream bug assigned to mhulan
Comment 4 Bryan Kearney 2016-08-04 14:17:19 UTC 
Upstream bug component is Reporting
Comment 5 Bryan Kearney 2016-08-04 14:17:21 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14154 has been closed
Comment 9 Ohad Levy 2016-08-08 13:25:30 UTC 
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).
Comment 10 jcallaha 2016-08-12 21:48:20 UTC 
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.
Comment 12 errata-xmlrpc 2016-08-16 07:11:46 UTC 
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