Bug 2062522

Summary: No data found for memory swap on Virtualization Overview
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Phillip Bailey <phbailey>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.10-rc3CC: aos-bugs, gouyang, phbailey
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-17 22:54: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:
Attachments:
Description Flags
video about memory swap none

Description Guohua Ouyang 2022-03-10 04:18:09 UTC
Created attachment 1865046 [details]
video about memory swap

Description of problem:
Create a Fedora VM and generate some data for swap memory metrics, the data is visible on Observe -> Dashboards, but is not visible on Virtualization -> Overview.

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

How reproducible:


Steps to Reproduce:
1. Create a Fedora VM
2. Install stress-ng in the VM
3. Run 'stress-ng --vm 2 --vm-bytes 90% --vm-method all -t 15m' in the VM


Actual results:
No data available on Virtualization -> Overview.

Expected results:
Data is visible on Virtualization -> Overview.

Additional info:
the data is visible on Observe -> Dashboards

Comment 1 Guohua Ouyang 2022-11-03 01:51:20 UTC
verified on 4.10.0-0.nightly-2022-11-01-183141

Comment 4 errata-xmlrpc 2022-11-17 22:54:06 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 (OpenShift Container Platform 4.10.41 bug fix update), 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-2022:7866