Bug 2184920

Summary: KubeVirtComponentExceedsRequestedMemory Alert for virt-operator pod
Product: Container Native Virtualization (CNV) Reporter: Akriti Gupta <akrgupta>
Component: VirtualizationAssignee: ffossemo
Status: CLOSED ERRATA QA Contact: Akriti Gupta <akrgupta>
Severity: high Docs Contact:
Priority: high    
Version: 4.13.0CC: acardace
Target Milestone: ---Flags: akrgupta: needinfo+
Target Release: 4.13.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry-container-v4.13.1.rhel9-37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-20 13:41:05 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
KubeVirtComponentExceedsRequestedMemory- virt-operator none

Description Akriti Gupta 2023-04-06 08:09:35 UTC
Created attachment 1956060 [details]
KubeVirtComponentExceedsRequestedMemory- virt-operator

Description of problem:
KubeVirtComponentExceedsRequestedMemory Alert for virt-operator shows actual memory higher than requested memory,
actual memory: 860.1M
Requested memory: 471.9M
as shown in the graph in attachment

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 sgott 2023-04-06 11:58:38 UTC
Estimating this BZ has a high severity as memory use is double what was expected under presumably normal conditions.

Akriti, would you perchance still have the cluster available? Or at least a must-gather report?

Comment 4 Antonio Cardace 2023-04-11 15:19:56 UTC
@akrgupta can you describe what you did to reach that memory usage? Did you update the KubeVirt CR multiple times for example? How many vms did you create? Can you do a must-gather of the cluster? How reproducible is this?

Comment 12 errata-xmlrpc 2023-06-20 13:41:05 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 Virtualization 4.13.1 Images), 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/RHEA-2023:3686