-
Bug
-
Resolution: Done-Errata
-
Normal
-
CNV v4.16.0
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
CNV v4.99.0.rhel9-735, CNV v4.17.0.rhel9-196
-
-
1
-
CNV I/U Operators Sprint 254, CNV I/U Operators Sprint 255, CNV I/U Operators Sprint 256, CNV I/U Operators Sprint 257
-
Moderate
-
No
Description of problem:
metrics kubevirt_vmi_number_of_outdated: ndication for the total number of VirtualMachineInstance workloads that are not running within the most up-to-date version of the virt-launcher environment. Type: Gauge.
the data that is fetched is coming from virt-controller pods, in normal cluster we have more tan one pod, so each pod will show zero.
oc exec -n openshift-monitoring prometheus-k8s-0 -c prometheus – curl -s http://127.0.0.1:9090/api/v1/query?query=kubevirt_vmi_number_of_outdated | jq .
{
"status": "success",
"data": {
"resultType": "vector",
"result": [
{
"metric":
,
"value": [
1716312231.545,
"0"
]
},
{
"metric":
,
"value": [
1716312231.545,
"0"
]
}
]
}
Version-Release number of selected component (if applicable):
cnv- v4.17
How reproducible:
100%
Steps to Reproduce:
1.create cluster 2.run the metrics 3.
Actual results:
Expected results:
expected to see one indicator of the total outdated vm, not two indicators
Additional info:
- blocks
-
CNV-38391 [QE] add coverage for metric 'kubevirt_vmi_number_of_outdated'
-
- In Progress
-
- links to
-
RHEA-2024:133097 OpenShift Virtualization 4.17.0 Images
- mentioned on