+++ This bug was initially created as a clone of Bug #2026431 +++ Description of problem: There are 2 SSP alerts (SSPDown and SSPTemplateValidatorDown) are constantly in firing state right after cluster installation Metrics kubevirt_ssp_template_validator_up_total and kubevirt_ssp_operator_up_total show 0 However pods are active and in Running state: $ oc get pod -n openshift-cnv | egrep "ssp|template" ssp-operator-6557957df8-p7rhb 1/1 Running 6 (21h ago) 38h virt-template-validator-5dc6645f69-5q92b 1/1 Running 0 38h virt-template-validator-5dc6645f69-x57g5 1/1 Running 0 38h Version-Release number of selected component (if applicable): 4.9.1 Steps to Reproduce: 1. install cnv 2. wait 5-10 minutes 3. check alerts Actual results: SSPDown and SSPTemplateValidatorDown alerts are constantly in firing state Expected results: Alerts should fire only when SSP PODs are not active Additional info:
Verified on CNV v4.10.0-439 (kubevirt-ssp-operator v4.10.0-23) - no SSP alerts firing on a healthy cluster
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 (Moderate: OpenShift Virtualization 4.10.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-2022:0947