Bug 2209046
| Summary: | kubevirt_vmi_cpu_affinity metric is enriched with an excessive amount of labels | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Shirly Radco <sradco> |
| Component: | Metrics | Assignee: | João Vilaça <jvilaca> |
| Status: | CLOSED ERRATA | QA Contact: | Ahmad <ahafe> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.12.2 | CC: | dbasunag, jvilaca, kmajcher, stirabos |
| Target Milestone: | --- | ||
| Target Release: | 4.14.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | hco-bundle-registry-container-v4.14.0.rhel9-1744 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-08 14:05:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Shirly Radco
2023-05-22 12:23:50 UTC
Please also backport to release-1.0 https://github.com/kubevirt/kubevirt/pull/10266 is still open, moving back to post @sradco @jvilaca @dbasunag according to https://github.com/kubevirt/kubevirt/pull/10266 & https://github.com/kubevirt/kubevirt/issues/9713 The metric 'kubevirt_vmi_cpu_affinity' is no longer appears, it was replaced with another different behavior metric "kubevirt_vmi_node_cpu_affinity" kubevirt_vmi_node_cpu_affinity: Number of VMI CPU affinities to node physical cores. Type: Gauge. do we still need a qa verify here? QA tested CNV-v4.14.0.rhel9-1991 OCP-4.14.0-ec.3 metric kubevirt_vmi_node_cpu_affinity works properly virsh # vcpupin 1 VCPU CPU Affinity ---------------------- 0 0-7 virsh # vcpuinfo 1 VCPU: 0 CPU: 2 State: running CPU time: 36.9s CPU Affinity: yyyyyyyy [cloud-user@ocp-psi-executor ahmad]$ oc exec -n openshift-monitoring prometheus-k8s-0 -c prometheus -- curl -s http://127.0.0.1:9090/api/v1/query?query=kubevirt_vmi_node_cpu_affinity | jq . { "status": "success", "data": { "resultType": "vector", "result": [ { "metric": { "__name__": "kubevirt_vmi_node_cpu_affinity", "container": "virt-handler", "endpoint": "metrics", "instance": "10.129.2.82:8443", "job": "kubevirt-prometheus-metrics", "kubernetes_vmi_label_kubevirt_io_domain": "vm-cirros-datavolumes", "kubernetes_vmi_label_kubevirt_io_nodeName": "c01-ahmad414-rvpjr-worker-0-bptzv", "name": "vm-cirros-datavolumes", "namespace": "default", "node": "c01-ahmad414-rvpjr-worker-0-bptzv", "pod": "virt-handler-tkfp5", "service": "kubevirt-prometheus-metrics" }, "value": [ 1695051423.341, "8" ] } ] } } [cloud-user@ocp-psi-executor ahmad]$ 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.14.0 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-2023:6817 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |