Bug 1745877

Summary: missed ")" for "Memory Usage (Swap" on grafana "Kubernetes / Compute Resources / Namespace (Pods)" page
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Pawel Krupa <pkrupa>
Status: CLOSED ERRATA QA Contact: Viacheslav <mviaches>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.0CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1751440 (view as bug list) Environment:
Last Closed: 2019-10-16 06:37:54 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:
Bug Depends On:    
Bug Blocks: 1751440    
Attachments:
Description Flags
"Memory Usage (Swap" in page
none
issue is fixed, Memory Usage (Swap) none

Description Junqi Zhao 2019-08-27 06:43:29 UTC
Created attachment 1608382 [details]
"Memory Usage (Swap" in page

Description of problem:
grafana "Kubernetes / Compute Resources / Namespace (Pods)" page, Memory Quota part, "Memory Usage (Swap", missed ")" 

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-25-233755

How reproducible:
always

Steps to Reproduce:
1. 
2.
3.

Actual results:
"Memory Usage (Swap", missed ")" 

Expected results:
"Memory Usage (Swap)"
Additional info:

Comment 5 Viacheslav 2019-09-06 09:13:07 UTC
Still present on the 4.2.0-0.nightly-2019-09-05-234433

Comment 6 Junqi Zhao 2019-09-09 02:38:11 UTC
issue is fixed with 4.2.0-0.nightly-2019-09-08-180038, see the attached

Comment 7 Junqi Zhao 2019-09-09 02:38:48 UTC
Created attachment 1612975 [details]
issue is fixed, Memory Usage (Swap)

Comment 8 errata-xmlrpc 2019-10-16 06:37:54 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.

https://access.redhat.com/errata/RHBA-2019:2922