Bug 1292077

Summary: Containers Providers - Component Statuses table should not be shown when no data is available.
Product: Red Hat CloudForms Management Engine Reporter: Einat Pacifici <epacific>
Component: UI - OPSAssignee: Mooli Tayer <mtayer>
Status: CLOSED ERRATA QA Contact: Tony <ashlifst>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: cpelland, fsimonce, hkataria, jhardy, jprause, mpovolny, mtayer, obarenbo, srevivo
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.0Flags: ashlifst: needinfo+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: container
Fixed In Version: 5.6.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1292430 (view as bug list) Environment:
Last Closed: 2016-06-29 15:21:31 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:
Bug Depends On:    
Bug Blocks: 1292430    
Attachments:
Description Flags
CFME Containers Providers Component Statuses screenshot none

Description Einat Pacifici 2015-12-16 12:26:33 UTC
Created attachment 1106385 [details]
CFME Containers Providers Component Statuses screenshot

Description of problem:
In CFME Containers Providers page, the table titled:"Component Statuses" is visible with only the column names. 
This table should only be visible when there is data to populate the table. 

Version-Release number of selected component (if applicable):
5.5.0

How reproducible:
Always

Steps to Reproduce:
1.In CFME add a provider
2.Click on the provider
3.View the page information

Actual results:
A table titled: "Component Statuses" can be seen with only column headers, but no data in columns. 

Expected results:
The table should be invisible if no data is available. 

Additional info:
Screenshot provided.

Comment 2 Daniel Korn 2015-12-17 09:15:45 UTC
fix merged: https://github.com/ManageIQ/manageiq/pull/5514

Comment 5 errata-xmlrpc 2016-06-29 15:21:31 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/RHBA-2016:1348