Bug 1374450

Summary: Compliance check history isn't shown if compliance policy is unconditional
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ControlAssignee: Lucy Fu <lufu>
Status: CLOSED ERRATA QA Contact: Dmitry Misharov <dmisharo>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: dajohnso, dmisharo, jhardy, mfeifer, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.2   
Hardware: All   
OS: All   
Whiteboard: control:ui
Fixed In Version: 5.6.2.0 Doc Type: Bug Fix
Doc Text:
Previously, compliance check history wasn't shown if the compliance policy was unconditional. This occurred because a compliance detail record is required to display the compliance check history. With this fix, CloudForms now creates a compliance detail record for unconditional compliance policies, and the history is shown.
Story Points: ---
Clone Of: 1369488 Environment:
Last Closed: 2016-10-04 14:36:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Unknown Target Upstream Version:
Embargoed:
Bug Depends On: 1369488    
Bug Blocks:    

Comment 2 Dmitry Misharov 2016-09-14 12:42:39 UTC
I still can reproduce the issue. Tested on 5.6.2.0.20160913114355_70e9086. Compliance status and history is not shown in the web ui after compliance checking if a compliance policy is unconditional.

Comment 3 Lucy Fu 2016-09-14 13:15:18 UTC
Dmitry,

Can I take a look at your testing environment? 
Please send me the credentials of your server, if possible.

Comment 5 Dmitry Misharov 2016-09-14 13:21:51 UTC
Sorry, Lucy it was a mistake. The bug is verified in 5.6.2.0.20160913114355_70e9086

Comment 7 errata-xmlrpc 2016-10-04 14:36:23 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://rhn.redhat.com/errata/RHSA-2016-1996.html