Bug 2118367
| Summary: | KubeVirtComponentExceedsRequestedMemory Prometheus Rule is Failing to Evaluate | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Igor Bezukh <ibezukh> | ||||
| Component: | Virtualization | Assignee: | Igor Bezukh <ibezukh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Akriti Gupta <akrgupta> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.9.1 | CC: | acardace, cnv-qe-bugs, dcritch, dshchedr, gveitmic, ibezukh, kbidarka, kgordeev, kmajcher, ocasalsa, sgrunert, sradco, stirabos | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.10.5 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | hco-bundle-v4.10.5-3 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 2033077 | Environment: | |||||
| Last Closed: | 2022-09-06 14:02:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 2033077 | ||||||
| Bug Blocks: | 2118317 | ||||||
| Attachments: |
|
||||||
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 (Important: OpenShift Virtualization 4.10.5 Images security and bug fix update), 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/RHSA-2022:6351 ha! so now that this if fixed, I'm getting a ton of KubeVirtComponentExceedsRequestedMemory alerts: $ curl -s -k -H "Authorization: Bearer $(oc -n openshift-monitoring sa get-token prometheus-k8s)" https://$alert_url/api/v2/alerts | jq '.[] | select (.labels.alertname == "KubeVirtComponentExceedsRequestedMemory") | { alert: .labels.alertname, container: .labels.container, pod: .labels.pod }' { "alert": "KubeVirtComponentExceedsRequestedMemory", "container": "virt-controller", "pod": "virt-controller-756db895dc-67blj" } { "alert": "KubeVirtComponentExceedsRequestedMemory", "container": "virt-api", "pod": "virt-api-55c4f45f69-pgkmg" } { "alert": "KubeVirtComponentExceedsRequestedMemory", "container": "virt-operator", "pod": "virt-operator-6cdbf79fdc-d65jh" } { "alert": "KubeVirtComponentExceedsRequestedMemory", "container": "virt-operator", "pod": "virt-operator-6cdbf79fdc-m9p5z" } { "alert": "KubeVirtComponentExceedsRequestedMemory", "container": "virt-api", "pod": "virt-api-55c4f45f69-4s55p" } I tried to `customizeComponents`[0] but it didn't take the change. Maybe that option isn't in the `kubevirt.io/v1` API yet? Anyone else seeing these alerts after the update? [0] https://kubevirtlegacy.gitbook.io/user-guide/docs/operations/customize_components We have opened BZ for it: https://bugzilla.redhat.com/show_bug.cgi?id=2078545 oh nice. thanks for the link! |
Created attachment 1907546 [details] KubeVirtComponentExceedsRequestedMemory Verified with 4.10.5-6 no error message found