+++ This bug was initially created as a clone of Bug #2111794 +++

Description of problem:
tests/vmi_configuration_test.go:2950
the virtlogd process is taking too much RAM! (17468Ki > 17Mi). All processes: &map[libvirtd:{{28876800 0}

{<nil>} BinarySI} qemu-kvm:{{454934528 0} {<nil>}

BinarySI} virt-launcher:{{61800448 0}

{<nil>} BinarySI} virt-launcher-monitor:{{19357696 0} {<nil>}

BinarySI} virtlogd:{{17887232 0}

{<nil>} 17468Ki BinarySI}]
Expected
<int>: 1
to equal
<int>: -1
tests/vmi_configuration_test.go:3000

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

How reproducible:
Sometimes

Steps to Reproduce:
1. Run a VM
2.
3.

Actual results:


Expected results:


Additional info:

— Additional comment from Fabian Deutsch on 2022-07-28 08:30:51 UTC —

According to https://main-jenkins-csb-cnvqe.apps.ocp-c1.prod.psi.redhat.com/job/test-kubevirt-cnv-4.11-compute-ocs/354/testReport/junit/(root)/Tests%20Suite/_sig_compute_Configurations_virt_launcher_processes_memory_usage_should_be_lower_than_allocated_size/ this bug re-appeared:

tests/vmi_configuration_test.go:2950
the virtlogd process is taking too much RAM! (17468Ki > 17Mi). All processes: &map[libvirtd:{{28876800 0} {<nil>}

BinarySI} qemu-kvm:{{454934528 0}

{<nil>} BinarySI} virt-launcher:{{61800448 0} {<nil>}

BinarySI} virt-launcher-monitor:{{19357696 0}

{<nil>} BinarySI} virtlogd:{{17887232 0} {<nil>}

17468Ki BinarySI}]
Expected
<int>: 1
to equal
<int>: -1
tests/vmi_configuration_test.go:3000

— Additional comment from Fabian Deutsch on 2022-08-25 08:26:30 UTC —

Let's please pulls this into 4.11.z

— Additional comment from errata-xmlrpc on 2022-09-01 10:08:05 UTC —

This bug has been added to advisory RHEA-2022:101182 by Continuous Infra Team Autobot (contra/pipeline@REDHAT.COM)