Bug 1308938

Summary: System shows '1 action' while no actions available
Product: Red Hat CloudForms Management Engine Reporter: Vadim Rutkovsky <vrutkovs>
Component: Red Hat AccessAssignee: Keith Robertson <kroberts>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: cpelland, ihands, jhardy, jmoran, lphiri
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:access
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 14:48:00 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:
Attachments:
Description Flags
Screenshot none

Description Vadim Rutkovsky 2016-02-16 14:12:07 UTC
Created attachment 1127608 [details]
Screenshot

Description of problem:
System with no actions to perform still has an icon with '1 Action' title on Systems tab of Red Hat Insights

Version-Release number of selected component (if applicable):
cfme-5.5.2.4-1.el7cf.x86_64
rh-ruby22-rubygem-redhat_access_cfme-0.0.7-1.el7cf.noarch

How reproducible:
Always

Steps to Reproduce:
1. Subscribe an appliance and a latest updated rhel6 Vm to the same account
2. Run SSA on VM
3. Check 'Red Hat Insight' - 'Systems'
   The system has a warn icon with '1 Action' title
4. Click on the warn icon
   A panel with 'no action' appears
5. Check the warn icon title
   The systems has a warn icon with '0 Actions' title
6. Click 'Without actions' button
   The system is listed, has a warn icon with '0 Actions' title
7. Click "With actions" and "Without actions" again
   The system is listed, has an OK icon with '0 Actions' title

Actual results:
Icons are not changed as expected

Expected results:
Icons are changed when an according tab is opened

Additional info:

Comment 1 Dave Johnson 2016-02-18 14:48:00 UTC

*** This bug has been marked as a duplicate of bug 1308936 ***