Bug 1539370 - remove container statuses table from pod summary page
Summary: remove container statuses table from pod summary page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: GA
: 5.10.0
Assignee: Bronagh Sorota
QA Contact: Tony Khamis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-28 12:05 UTC by Oved Ourfali
Modified: 2019-02-07 23:01 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:01:05 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
container statuses (149.71 KB, image/png)
2018-01-28 12:08 UTC, Oved Ourfali
no flags Details
5 container statuses (201.86 KB, image/png)
2018-01-29 09:24 UTC, Ari Zellner
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:01:11 UTC

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 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


Note You need to log in before you can comment on or make changes to this bug.