Bug 1247627

Summary: [RFE] pod list in "browse" tab shows spinning icon which is confusing
Product: OpenShift Container Platform Reporter: Erik M Jacobs <ejacobs>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED ERRATA QA Contact: Yanping Zhang <yanpzhan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.0.0CC: dmcphers, jforrest, jokerman, libra-bugs, libra-onpremise-devel, mmccomas
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 13:22:48 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
Replacing fa-refresh with pficon-running
none
Replacing fa-refresh with pficon-running with motion
none
Travis build in progress indicator
none
Jenkins build in progress indicator
none
Newer Jenkins build in progress indicator
none
Jenkins Blue Ocean build in progress indicator (animated gif)
none
Jenkins Blue Ocean build progress indicator 2 (animated gif)
none
Pods list in v3.7 none

Description Erik M Jacobs 2015-07-28 13:17:31 UTC
If you go into the web UI and go to the "Browse" tab and then select "Pods", you will see that a running pod has the "fa-spin" spinning circle arrow.

This is confusing because we use the same icon during builds. Builds represent something about to be in transition.

I understand that the spinning icon is used throughout the UI to indicate "running", but, as with the status of build being "running" (https://github.com/openshift/origin/issues/3847) there is some confusing/missing context.

I think it would be better to adopt a color scheme dot for the pod status that also should match whatever colors we use on the overview tab to indicate pod health / pod status.

green = healthy
yellow = unhealthy (perhaps not yet ready, etc)
red = failed / warning (perhaps couldn't schedule, failed health check, etc)

and so on and so forth.

This would be a much more "expected" user experience.

Comment 2 Jessica Forrester 2016-12-09 21:01:24 UTC
@rhamilto one you can ponder, the answer may be we don't change anything but we should consider it

Comment 3 Robb Hamilton 2016-12-13 13:42:07 UTC
Created attachment 1231209 [details]
Replacing fa-refresh with pficon-running

Comment 4 Robb Hamilton 2016-12-13 13:43:15 UTC
Created attachment 1231211 [details]
Replacing fa-refresh with pficon-running with motion

Comment 5 Robb Hamilton 2016-12-13 13:44:13 UTC
The sole use of color is problematic for colorblind users (estimates are as high as 10% of the male population), so I think we'll also need to consider shape and/or motion as well.  

Brainstorming:  PatternFly includes a "running" icon (see pficon-running at https://www.patternfly.org/styles/icons), which we could use in place of the existing fa-refresh. Coupled with the addition of color and retaining the current rules regarding motion (spin) [1], this could be a step towards improvement.  See attachments.

[1] if there are more than one status icons on the page, the motion is disabled (e.g., browse/pods)

Comment 6 Jessica Forrester 2016-12-13 21:51:07 UTC
Agreed that color only is not an option.

I'm curious if the patternfly folks intended that icon to be used without motion?  I'm not sure I would see that in its static state and get 'running' from it.  Whereas refresh is able to indicate motion even when it's static.

Comment 7 Robb Hamilton 2016-12-14 16:27:08 UTC
Given that we also use fa-refresh to indicate active deployments, what if we switch builds to pficon-running instead of pods?  That way, we retain the meaning for both deployments and pods, but create a unique instance for builds (since it seems to be the outlier)?  It seems we could always spin pficon-running for builds (thus alleviating the concern about the icon not indicating 'running') since a build has a finite time span and won't typically have multiples running concurrently?

Comment 8 Robb Hamilton 2016-12-14 20:54:41 UTC
Created attachment 1231882 [details]
Travis build in progress indicator

Food for thought:  Travis uses this animated "icon" to indicate a build is running.

Comment 9 Robb Hamilton 2016-12-14 20:55:38 UTC
Created attachment 1231883 [details]
Jenkins build in progress indicator

Food for thought:  Jenkins uses this animated "icon" to indicate a build is running.

Comment 10 Samuel Padgett 2016-12-14 21:03:44 UTC
I'm not sure we should have different icons for the same status labels like "Running." They also show together on the monitoring page, which might look odd.

(In reply to Erik M Jacobs from comment #0)

> I think it would be better to adopt a color scheme dot for the pod status
> that also should match whatever colors we use on the overview tab to
> indicate pod health / pod status.
> 
> green = healthy
> yellow = unhealthy (perhaps not yet ready, etc)
> red = failed / warning (perhaps couldn't schedule, failed health check, etc)
> 
> and so on and so forth.
> 
> This would be a much more "expected" user experience.

For what it's worth, we've done something like this already. Pods with crashing containers now have a red `X` and status displayed even though the pod is "Running." So you can see when a pod is unhealthy directly from this list. We also show the number of containers ready in the table.

Comment 11 Robb Hamilton 2016-12-15 16:50:48 UTC
Created attachment 1232278 [details]
Newer Jenkins build in progress indicator

Comment 12 Robb Hamilton 2017-06-29 18:25:54 UTC
Created attachment 1292950 [details]
Jenkins Blue Ocean build in progress indicator (animated gif)

Comment 13 Robb Hamilton 2017-06-29 18:36:02 UTC
Created attachment 1292954 [details]
Jenkins Blue Ocean build progress indicator 2 (animated gif)

Comment 14 Robb Hamilton 2017-10-25 14:33:22 UTC
Created attachment 1343295 [details]
Pods list in v3.7

With the upcoming 3.7 release, the browse pods table has been revised since this bug was originally filed.

* the running icons no longer spin
* unhealthy pods get a red x icon instead of the refresh icon

Erik, are these changes sufficient to address your concerns?

Comment 15 Jessica Forrester 2017-11-01 18:43:06 UTC
At this point our users are going to expect the refresh icon to indicate a running pod on this page.  I don't anticipate changing this significantly.  As already mentioned we've addressed the "running but crashing" scenario, so marking MODIFIED for that reason.

Comment 16 Robb Hamilton 2017-11-06 14:49:54 UTC
PR to resolve: https://github.com/openshift/origin/pull/6083

Comment 18 Yanping Zhang 2017-12-06 09:16:02 UTC
Checked on 3.7 env with version v3.7.13.
Now on pods page, the status icon for running pods is a refresh icon and doesn't spin. The status icon for failed pod is a red x.
According to comment 14, these are all the fixes for the bug, so I'd like to move the bug to Verified.

Comment 21 errata-xmlrpc 2017-12-18 13:22:48 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-2017:3464