Bug 1804141 - Monitoring Dashboards: Current Status table is not rendered in cluster-total dashboard
Summary: Monitoring Dashboards: Current Status table is not rendered in cluster-total ...
Keywords:
Status: CLOSED DUPLICATE of bug 1804733
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.0
Assignee: Andrew Pickering
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 10:18 UTC by Yadan Pei
Modified: 2023-09-14 05:52 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-19 21:36:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yadan Pei 2020-02-18 10:18:49 UTC
Description of problem:
'Current Status' table is empty on cluster-total dashboard page

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-02-17-211020

How reproducible:
Always

Steps to Reproduce:
1. cluster admin user choose 'cluster-total' from Dashboard drop down on Monitoring -> Dashboard page, check the tables & charts

Actual results:
1. Current Status table is not rendered and shown

Expected results:
1. 'Current Status' table should be rendered correctly as in Grafana console

Additional info:

Comment 1 bpeterse 2020-02-19 21:36:23 UTC

*** This bug has been marked as a duplicate of bug 1804733 ***

Comment 2 Yadan Pei 2020-02-20 10:00:39 UTC
Hi Ben,

May I ask why 1804141 is closed as a DUP of 1804733? I saw 1804733 was created after 1804141

Comment 3 Yadan Pei 2020-02-20 10:06:44 UTC
except for some differences in comments, I don't see other differences between the two bugs

Comment 4 Red Hat Bugzilla 2023-09-14 05:52:51 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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