Bug 1731202

Summary: RAM consumption in Operator Console has misleading unit
Product: OpenShift Container Platform Reporter: Simon Reber <sreber>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, nmukherj
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-19 09:11:52 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
Screenshot from Pod Overview none

Description Simon Reber 2019-07-18 15:27:28 UTC
Created attachment 1591823 [details]
Screenshot from Pod Overview

Description of problem:

In OpenShift Container Platform 3.11, the Operator (Cluster) Console shows misleading unit for the RAM graph.

Within the `Pod Overview` the unit for RAM is reported as `B` if the range is within GB range.

This is fairly misleading as it could also mean Byte or something else and does not properly reflect the GB unit.

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

- openshift v3.11.98
- kubernetes v1.11.0+d4cacc0

How reproducible:

- Always

Steps to Reproduce:
1. Install OpenShift Container Platform 3.11 with Prometheus
2. Start pod
3. Check pod Overview in Cluster Console and verify the unit for RAM

Actual results:

Unit is set to 4B if the pod is using 4 GB

Expected results:

Unit should be set to 4GB if the pod is using 4 GB

Additional info:

Comment 1 Samuel Padgett 2019-07-19 09:11:52 UTC

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