Flakey test - Prometheus Alerts SSPHighRateRejectedVms Alert [test_id:8377] Should fire SSPHighRateRejectedVms

[lyarwood]

What happened:

https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/kubevirt_ssp-operator/952/pull-ci-kubevirt-ssp-operator-main-e2e-single-node-functests/1778701297726263296

Prometheus Alerts SSPHighRateRejectedVms Alert [test_id:8377] Should fire SSPHighRateRejectedVms
/go/src/github.com/kubevirt/ssp-operator/tests/monitoring_test.go:116
  [FAILED] in [It] - /go/src/github.com/kubevirt/ssp-operator/tests/monitoring_test.go:123 @ 04/12/24 09:32:57.388
• [FAILED] [634.636 seconds]
Prometheus Alerts SSPHighRateRejectedVms Alert [It] [test_id:8377] Should fire SSPHighRateRejectedVms
/go/src/github.com/kubevirt/ssp-operator/tests/monitoring_test.go:116
  [FAILED] Timed out after 600.000s.
  Unexpected error:
      <*errors.errorString | 0xc000ce21c0>: 
      alert SSPHighRateRejectedVms not found
      {
          s: "alert SSPHighRateRejectedVms not found",
      }
  occurred
  In [It] at: /go/src/github.com/kubevirt/ssp-operator/tests/monitoring_test.go:123 @ 04/12/24 09:32:57.388

What you expected to happen: A clear and concise description of what you expected to happen.

How to reproduce it (as minimally and precisely as possible): Steps to reproduce the behavior.

Additional context: Add any other context about the problem here.

Environment:

• KubeVirt version (use virtctl version): N/A
• Kubernetes version (use kubectl version): N/A
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: N/A
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others: N/A

[kubevirt-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[akrejcir]

/remove-lifecycle rotten

[akrejcir]

Closing, because the test is not failing currently.

We can reopen if it happens again.