Bug 1382847

Summary: Compliance history is broken for a VM
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED ERRATA QA Contact: Dmitry Misharov <dmisharo>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: cpelland, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.3   
Hardware: All   
OS: All   
Whiteboard: control
Fixed In Version: 5.6.3.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1375093 Environment:
Last Closed: 2016-11-30 19:56:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1375093    
Bug Blocks:    

Comment 2 CFME Bot 2016-10-08 15:21:10 UTC 
New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/e89af64b2811d613aa356c872006adcfdaf3eff1

commit e89af64b2811d613aa356c872006adcfdaf3eff1
Author:     Dan Clarizio <dclarizi>
AuthorDate: Wed Sep 28 15:49:53 2016 -0700
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Sat Oct 8 09:25:41 2016 -0400

    Merge pull request #11564 from h-kataria/vm_compliance_history_link_fix
    
    Vm compliance history link fix
    (cherry picked from commit 3a730261dd15773434816bf3795d1f4928d81e88)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1382847

 app/helpers/compliance_summary_helper.rb       |  3 +-
 spec/helpers/compliance_summary_helper_spec.rb | 64 ++++++++++++++++++++++++++
 2 files changed, 66 insertions(+), 1 deletion(-)
 create mode 100644 spec/helpers/compliance_summary_helper_spec.rb
Comment 3 Dmitry Misharov 2016-11-10 08:21:32 UTC 
Fixed and verified in 5.6.3.0.20161108115816_66df924. Compliance status and history are shown correctly.
Comment 5 errata-xmlrpc 2016-11-30 19:56:33 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-2839.html