Bug 1257740 - Reported times in OpenSCAP 'Compliance Reports' list are wrong
Reported times in OpenSCAP 'Compliance Reports' list are wrong
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Beta
: --
Assigned To: Shlomi Zadok
Kedar Bidarkar
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-08-27 15:48 EDT by Maxim Burgerhout
Modified: 2017-05-18 13:32 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-27 05:18:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Maxim Burgerhout 2015-08-27 15:48:39 EDT
Description of problem:
I just ran an OpenSCAP test, and manually made sure the report was uploaded to Satellite. The 'date' column on the 'Compliance Reports' page shows 'about 20 hours ago', but that's clearly not right.

The report itself shows the correct time though.

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

How reproducible:

Steps to Reproduce:
1. Create SCAP content, policy
2. Manually run foreman_scap_client and smart-proxy-openscap-send

Actual results:
'Date' column on 'compliance reports' page shows 'about 20 hours ago'

Expected results:
Should be more like 3 minutes

Additional info:
Comment 1 Bryan Kearney 2015-08-28 13:35:17 EDT
Created redmine issue http://projects.theforeman.org/issues/11603 from this bug
Comment 3 Bryan Kearney 2015-11-01 06:02:05 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/11603 has been closed
Comment 7 Kedar Bidarkar 2016-03-31 15:30:58 EDT
We can now see the compliance report "reported at" column in minutes and not just hours.

VERIFIED With sat62-snap6
Comment 9 errata-xmlrpc 2016-07-27 05:18:19 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.