-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
None
-
0.42
-
False
-
-
False
-
CNV v4.99.0.rhel9-708, CNV v4.17.0.rhel9-164, CNV v4.16.1.rhel9-20
-
---
-
---
-
-
CNV I/U Operators Sprint 254, CNV I/U Operators Sprint 255, CNV I/U Operators Sprint 256, CNV I/U Operators Sprint 257
-
No
Description of problem:
The expression of the alert LowReadyVirtOperatorsCount is: kubevirt_virt_operator_ready < kubevirt_virt_operator_up The problem is with the kubevirt_virt_operator_ready which give wrong value. When making the virt-operator pods to be in running state but not ready the metric still give the value of the number of pods running even that it is in not ready state.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
100%
Steps to Reproduce:
1.go to the CSV of CNV, and update the ..containers[0].readinessProbe.httpGet.path of the virt-operator deployment to something else than /metrics , e.g. /metrics-fake. 2.Delete the replicaSet of the virt-operator 3.Check the metric kubevirt_virt_operator_ready.
Actual results:
The kubevirt_virt_operator_ready give the value like the running pods.
Expected results:
The value should be 0, since the pods is not ready
Additional info:
Added Screenshots
- links to
-
RHEA-2024:136034
OpenShift Virtualization 4.16.1 Images
- mentioned on
