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.

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):
ruby193-rubygem-foreman_openscap-0.3.2.10-1.el7sat.noarch
foreman-1.7.2.33-1.el7sat.noarch

How reproducible:


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

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

Expected results:
Should be more like 3 minutes

Additional info:

Created redmine issue http://projects.theforeman.org/issues/11603 from this bug

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

We can now see the compliance report "reported at" column in minutes and not just hours.

VERIFIED With sat62-snap6

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:1501