Description of problem: Alert SSPDown is constantly in firing state right after cluster installation Metric kubevirt_ssp_operator_up_total shows 0 available pods, however ssp-operator pod is running: $ oc get pod -n openshift-cnv | grep ssp ssp-operator-78765556ff-mm6n6 1/1 Running 0 164m Version-Release number of selected component (if applicable): 4.11 Steps to Reproduce: 1. install CNV 2. wait 5-10 minutes 3. check alerts Actual results: SSPDown alert is in firing state Expected results: Alerts should fire only when ssp-operator pods is not active Additional info: The issue looks very similar to this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2026431
Verified on CNV v4.11.0-445 (kubevirt-ssp-operator v4.11.0-47) - SSPDown alert is not triggered on 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 (Important: OpenShift Virtualization 4.11.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:6526