Bug #11603

Reported times in OpenSCAP 'Compliance Reports' list are wrong

Added by Bryan Kearney about 2 years ago. Updated about 2 years ago.

Status:ClosedSpent time:-
Priority:Normal
Assigned To:-
Category:-
Target version:0.5.0
Difficulty: Bugzilla link:1257740
Found in release: Pull request:https://github.com/theforeman/foreman_openscap/pull/135
Triaged:No
Story points-
Velocity based estimate-

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:

History

#1 Updated by Shlomi Zadok about 2 years ago

related to #11421
We need to send the full date & time (currently sending date only)

#2 Updated by Shlomi Zadok about 2 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

This was fixed on the smart_proxy_openscap, yet should be verified from foreman_openscap#arf_report PR

#3 Updated by Shlomi Zadok about 2 years ago

  • % Done changed from 0 to 100

#4 Updated by Shlomi Zadok about 2 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF