Bug 1979562 - Cluster operators: don't show messages when neither progressing, degraded or unavailable
Summary: Cluster operators: don't show messages when neither progressing, degraded or ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Cyril
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2021-07-06 12:16 UTC by Stefan Schimanski
Modified: 2022-03-12 04:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-12 04:35:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
ClusterOperators message (417.75 KB, image/png)
2021-09-22 07:01 UTC, Yadan Pei
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 9790 0 None None None 2021-08-11 17:18:27 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:36:15 UTC

Description Stefan Schimanski 2021-07-06 12:16:34 UTC
In console, the cluster operators have non-uniform condition messages if they are neither progressing, degraded nor unavailable. This doesn't look good:


In contrast, `oc get co` uses server-side column view, which hides those messages when non of the conditions is triggered.

Comment 3 Yadan Pei 2021-09-22 07:01:31 UTC
Created attachment 1825220 [details]
ClusterOperators message

When ClusterOperator is in Available status, console only shows '-' in message column, otherwise it will show the status message.

Verified on 4.10.0-0.nightly-2021-09-21-181111

Comment 4 Yadan Pei 2021-09-22 07:02:21 UTC
sorry, changing assignee back

Comment 8 errata-xmlrpc 2022-03-12 04:35:46 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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