Or Shoval

/retest-required

lately this happens here and there `09:36:12: Error from server: error when creating "/home/prow/go/src/github.com/kubevirt/kubevirt/_out/manifests/release/kubevirt-cr.yaml": etcdserver: request timed out`

seems cluster-down failed but tests passed first time i see it, so no biggie for now https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11261/pull-kubevirt-e2e-k8s-1.27-sig-compute/1762077379578040320 ``` 15:58:55: selecting podman as container runtime 15:58:56: Error response from daemon: getting...

/test pull-kubevirt-e2e-k8s-1.27-sig-compute

/test pull-kubevirt-e2e-k8s-1.29-swap-enabled

https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11188/pull-kubevirt-e2e-k8s-1.29-swap-enabled/1755587001714741248 it is with skip_report=true, this is why it doesnt appear here even after triggering 1 failure, lets see if it is a flake or due to the PR

/test pull-kubevirt-e2e-k8s-1.29-swap-enabled https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/11188/pull-kubevirt-e2e-k8s-1.29-swap-enabled/1755598125134778368

Made sure that it also fails on clean main so it is not this PR https://github.com/kubevirt/kubevirt/pull/11190#issuecomment-1934315788 (test is known to be flaky due to the stress that it runs) opened...

/sig code-quality

Addressed comments