Bug #11603: Reported times in OpenSCAP 'Compliance Reports' list are wrong - OpenSCAP - Foreman

Actions

Copy link

Bug #11603

closed

Reported times in OpenSCAP 'Compliance Reports' list are wrong

Added by Bryan Kearney over 9 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Target version:

0.5.0

Difficulty:

Triaged:

Bugzilla link:

1257740

Pull request:

https://github.com/theforeman/foreman_openscap/pull/135

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1257740
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:

Updated by Shlomi Zadok over 9 years ago

Status changed from New to Ready For Testing
Target version set to 0.5.0
Pull request https://github.com/theforeman/foreman_openscap/pull/135 added
Pull request deleted ()