Bug 1792489 - Console should give better indication on nodes/machines/pods how long exceptional states (pending, failed, stopped) have persisted for
Summary: Console should give better indication on nodes/machines/pods how long excepti...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Steve Goodwin
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-17 17:28 UTC by Clayton Coleman
Modified: 2020-02-04 16:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-04 16:58:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clayton Coleman 2020-01-17 17:28:00 UTC
If I stop a node, it is not ready and that is displayed at the top of the console page for the node status, which is good.  However, the time that exceptional error condition has persisted is not easy to see and is very important.  We need to draw attention to how long nodes, pods, and machines (at least) in error/abnormal states (i.e. by visually hoisting the time since that transition happened, or by visually emphasizing the time on the page, or some other mechanism).

Expected to quickly (at a glance) understand from the node details page how long a down node had been down for.

Comment 1 Stephen Cuppett 2020-01-17 18:06:46 UTC
Setting target release to the active development branch (4.4). For fixes, if any, which require backport to prior versions, clones of this BZ will be created.

Comment 2 bpeterse 2020-02-04 16:58:32 UTC
Promoting this to an RFE so we can plan for the work in a future release:

https://issues.redhat.com/browse/RFE-563?filter=12344731


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