-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
3
-
False
-
-
False
-
NoActiveCustomerTickets
-
CLOSED
-
---
-
---
-
CNV Virtualization Sprint 231, CNV Virtualization Sprint 232, CNV Virtualization Sprint 233, CNV Virtualization Sprint 234, CNV Virtualization Sprint 235
-
High
-
None
Description of problem:
There are many alerts KubeVirtComponentExceedsRequestedMemory in Firing state on a cluster, some of them appeared right after installation.
May be memory should be adjusted for kubevirt system pods?
Version-Release number of selected component (if applicable):
4.11
Actual results:
Alerts are constantly firing, some of them triggered right after cluster installation. Screenshot attached
Expected results:
kubevirt system pods requested enough memory and alert is not triggered
- blocks
-
CNV-24915 [2166385] many KubeVirtComponentExceedsRequestedMemory alerts in Firing state
- Closed
- external trackers
(9 external trackers)