Bug 1840861

Summary: Charts in the Node Details tab duplicate information found in the Node Overview tab
Product: OpenShift Container Platform Reporter: Andy Braren <abraren>
Component: Management ConsoleAssignee: Rastislav Wagner <rawagner>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, jokerman, rawagner, yanpzhan
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:42:22 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:

Description Andy Braren 2020-05-27 18:05:57 UTC
Description of problem:

The new Node Overview's Utilization card was intended to replace the charts that appear in the Details tab, since it includes more information about limits/requests and available resources and is consistent with Cluster/Project/Host Overviews. The charts in the Details tab haven't been removed yet.

Version-Release number of selected component (if applicable):

How reproducible:
Navigate to Compute > Nodes > Node Details. The Overview tab's Utilization card has more information than the charts at the top of the Details tab.

Steps to Reproduce:
1. Navigate to a Node Details page
2. Compare the charts shown in the Overview and Details tabs

Actual results:
The Details tab has charts for CPU/Memory/Pods/Network/Filesystem.

Expected results:
The Details tab shouldn't have those charts now that the Node Overview exists.

Additional info:

Comment 3 Yanping Zhang 2020-06-01 10:12:45 UTC
Checked on OCP 4.5 cluster with payload 4.5.0-0.nightly-2020-05-30-025738
Go to one node page, all charts are shown under "Overview" page, and check under "Details" tab, there is no metrics chart now.

Comment 4 errata-xmlrpc 2020-07-13 17:42:22 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.