On today's SIG CI test quarantine meeting we have noticed that sig-operator lanes are showing clustered failures on periodics and presubmits.

The first PR they showed up on was this one: https://github.com/kubevirt/kubevirt/pull/11969

The failures started to occur yesterday, so probably caused by a commit at or before https://github.com/kubevirt/kubevirt/commit/55fc278af78098e9f9ebb2c80f57209114b838ac

Links:

• flakefinder report
• https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-1.29-sig-operator/1795460141886214144
• https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-1.30-sig-operator/1795490338714947584
• https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11969/pull-kubevirt-e2e-k8s-1.28-sig-operator/1795443456441585664
• https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11969/pull-kubevirt-e2e-k8s-1.29-sig-operator/1795443457074925568
• https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11969/pull-kubevirt-e2e-k8s-1.30-sig-operator/1795493426263756800