Bug 1374450 - Compliance check history isn't shown if compliance policy is unconditional
Summary: Compliance check history isn't shown if compliance policy is unconditional
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Control
Version: 5.6.0
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.6.2
Assignee: Lucy Fu
QA Contact: Dmitry Misharov
URL:
Whiteboard: control:ui
Depends On: 1369488
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 17:22 UTC by Satoe Imaishi
Modified: 2022-07-09 07:53 UTC (History)
6 users (show)

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.
Clone Of: 1369488
Environment:
Last Closed: 2016-10-04 14:36:23 UTC
Category: ---
Cloudforms Team: Unknown
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1996 0 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 18:26:13 UTC

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
Note You need to log in before you can comment on or make changes to this bug.