-
Bug
-
Resolution: Unresolved
-
Normal
-
CNV v4.17.0
-
None
-
2
-
False
-
-
False
-
None
-
Yellow
-
Potential release note candidate
-
Unspecified Release Note Type - Unknown
-
Proposed
-
---
-
---
-
-
None
Description of problem:
We see that the kubevirt_vmi_launcher_memory_overhead_bytes metric is reporting incorrect results. It doesn't report the metric for each vm and is reporting for some of them multiple times.
Version-Release number of selected component (if applicable):
4.17
How reproducible:
Steps to Reproduce:
1. Check the kubevirt_vmi_launcher_memory_overhead_bytes metric results and compare them to the actual VMs. 2. 3.
Actual results:
Not reporting per VM the memory overhead
Expected results:
For each running VMI the metric should report a separate line with the correct memory overhead information.
Additional info:
- depends on
-
-
- Closed
-
