Bug 1539370

Summary: remove container statuses table from pod summary page
Product: Red Hat CloudForms Management Engine Reporter: Oved Ourfali <oourfali>
Component: ProvidersAssignee: Bronagh Sorota <bsorota>
Status: CLOSED ERRATA QA Contact: Tony Khamis <tkhamis>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.9.0CC: gblomqui, jfrey, jhardy, lavenel, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:01:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Attachments:
Description Flags
container statuses
none
5 container statuses none

Description Oved Ourfali 2018-01-28 12:05:39 UTC 
Description of problem:
In the container summary page, there is a section on the lower right specifying the "container statuses summary".

I discussed it last week with Loic and Barak.
According to Barak, there will always be "1" only in one of the rows specified in this summary (Waiting/Running/Terminated).

There is also a "Status" row in the "Properties" section, and there the value should map to the row with the "1" value in the container summary section.

If that's the case, please remove the "container statuses" section.

See Screenshot for clarification.
Comment 3 Oved Ourfali 2018-01-28 12:08:13 UTC 
Created attachment 1387168 [details]
container statuses
Comment 4 Ari Zellner 2018-01-29 09:24:32 UTC 
Created attachment 1387667 [details]
5 container statuses

1 running container is the usual case but in prometheus for example we have 5. 

I still think that we can remove that table. in most cases, its a waste of space.
Comment 5 Ari Zellner 2018-01-29 11:50:30 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/3332
Comment 6 Tony Khamis 2018-07-05 08:45:08 UTC 
Verified on version :  5.10.0.2.20180626170006_40dc459
Comment 8 errata-xmlrpc 2019-02-07 23:01:05 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/RHSA-2019:0212