-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
Quality / Stability / Reliability
-
False
-
False
-
CLOSED
-
CNV Virtualization Sprint 214, CNV Virtualization Sprint 215, CNV Virtualization Sprint 216, CNV Virtualization Sprint 217, CNV Virtualization Sprint 218, CNV Virtualization Sprint 219
-
Important
-
No
Description of problem:
Version: 4.10
There is no case when NoReadyVirtController or NoReadyVirtOperator are triggered. They are supposed to be fired when there is a virt-controller/virt-operator pod but it is not ready yet. Because of the alert definitions and metric implementations, `ready` metrics cannot be 0 and the alerts are not triggered.