Bug 2125198 - the virtlogd process is taking too much RAM! (17468Ki > 17Mi)
Summary: the virtlogd process is taking too much RAM! (17468Ki > 17Mi)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.2
Assignee: Jed Lejosne
QA Contact: Akriti Gupta
URL:
Whiteboard:
Depends On: 2111794
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-08 09:58 UTC by Antonio Cardace
Modified: 2023-01-12 14:09 UTC (History)
6 users (show)

Fixed In Version: hco-bundle-registry-container-v4.11.1-35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2111794
Environment:
Last Closed: 2023-01-12 14:08:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 8430 0 None open [release-0.53] Bump virtlogd memory requirement to 18Mi and libvirtd to 35Mi 2022-09-08 10:02:27 UTC
Red Hat Issue Tracker CNV-21121 0 None None None 2022-12-14 10:33:04 UTC
Red Hat Product Errata RHEA-2023:0155 0 None None None 2023-01-12 14:09:12 UTC

Comment 1 Kedar Bidarkar 2022-10-07 09:14:52 UTC 
Akriti, Make sure the Tier1 testcase related top this passes.
Comment 3 Akriti Gupta 2022-12-20 10:59:02 UTC 
moving this BZ to verified since Tier1 testcase related to this passes.
https://main-jenkins-csb-cnvqe.apps.ocp-c1.prod.psi.redhat.com/job/test-kubevirt-cnv-4.11-compute-ocs/537/testReport/(root)/Tests%20Suite/_sig_compute_Configurations_virt_launcher_processes_memory_usage_should_be_lower_than_allocated_size/
Comment 10 errata-xmlrpc 2023-01-12 14:08:55 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.11.2 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:0155
Note You need to log in before you can comment on or make changes to this bug.