Bug 1197841

Summary: [RFE] SmartState Analysis should collect installed date for RPMs
Product: Red Hat CloudForms Management Engine Reporter: Christian Jung <cbolz>
Component: SmartState AnalysisAssignee: Mo Morsi <mmorsi>
Status: CLOSED ERRATA QA Contact: Thom Carlin <tcarlin>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3.0CC: dajohnso, jhardy, obarenbo, roliveri
Target Milestone: GAKeywords: FutureFeature
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.5.0.6 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 13:03:21 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:

Description Christian Jung 2015-03-02 17:37:08 UTC
Description of problem:
SmartState Analysis collects quite a lot of useful data for installed packages on Linux systems (RPM based).

For security audits, it would be very useful to identify when a given package was installed. 

For example:
- RH is releasing errata XYZ
- some time passes...
- errata is installed on server X
- create a report to compare install date with errata release date to measure delays

For auditing it would be useful to track when a given package was installed on a given server. RPM provides the raw data to do this, but CF doesn't store it in its database.

rpm -qa --qf "%{INSTALLTIME} %{NAME}\n"

It would be nice if CF would also collect this data from the RPM database and store it in its VMDB.

Comment 2 Mo Morsi 2015-04-20 14:29:20 UTC
Patchset adding this feature has been submitted.

https://github.com/ManageIQ/manageiq/pull/2384

Comment 4 Dave Johnson 2015-11-17 14:48:57 UTC
Its now collected in the database but not visible in the web ui.  I opened bug 1282827 to track this.

Comment 6 errata-xmlrpc 2015-12-08 13:03:21 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/RHSA-2015:2551