Bug 1957420

Summary: Cluster Dashboard - Memory Utilisation has an error
Product: OpenShift Container Platform Reporter: jhusta <jhusta>
Component: MonitoringAssignee: Pawel Krupa <pkrupa>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: alegrand, alklein, anpicker, aos-bugs, brueckner, erooth, Holger.Wolf, jhusta, jokerman, kakkoyun, krmoser, lcosic, pkrupa, spadgett, surbania, wolfgang.voesch
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-07 09:56:06 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: 1934148    
Attachments:
Description Flags
Screen Shots from console none

Description jhusta 2021-05-05 18:22:39 UTC
Description of problem:
In Administrator view
Monitoring->Dashboard-> Kubernetes/Compute Resources/Cluster

Memory Utilisation Tile states 1:121:parse error:unterminated quoted string

Here is the string:
1 - sum(:node_memory_MemAvailable_bytes:sum{cluster=""}) / sum(kube_node_status_allocatable{resource="memory",cluster="""})

After deleting one of the " I get a value so easy fix.


I will attach a screen shot.






Version-Release number of selected component (if applicable):
Server Version: 4.8.0-0.nightly-s390x-2021-04-28-231853

How reproducible:
See above

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 jhusta 2021-05-05 18:24:07 UTC
Created attachment 1779939 [details]
Screen Shots from console

Comment 2 Samuel Padgett 2021-05-06 13:20:21 UTC
This dashboard query comes from the Grafana JSON dashboard definition maintained by the Monitoring team. Updating the component.

Comment 3 Junqi Zhao 2021-05-07 09:56:06 UTC

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