Or Mergi

> Looks good now, let's add it to the #4612 Done

Yep, close in favor of #4612 /close

Following https://github.com/kubevirt/kubevirt/issues/12898#issuecomment-2370242323 and #12934, we have the full error message in the following job: https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/12934/pull-kubevirt-e2e-k8s-1.29-sig-network/1839027779501297664 Error message: ``` { Failure tests/network/expose.go:701 Unexpected error: : failed running job against service with...

According to SearchCI [[1]](https://search.ci.kubevirt.io/?search=failed+running+job+against+service+with+ClusterIP&maxAge=336h&context=1&type=bug%2Bissue%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job), first occurrence of the these failures seen on sig-net periodic lane on 19 September [[2]](https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-1.29-sig-network/1836734599254773760). I went through most failing jobs mentioned so far, it looks...

I think in general sig-net is more prone to flakiness when there is a general slowness in the cluster, because it has tests that spins up multiple VMs, Jobs, pods,...

> There was no change to the number of jobs that we are running on the clusters - the number of parallel tests that each job can run at one...

@brianmcarey note that in the past week and a half (since 16 Oct.) there were holidays and naturally less burden on CI systems. Please consider starching monitoring time to additional...

/test pull-kubevirt-e2e-k8s-1.30-sig-network

/test pull-kubevirt-e2e-k8s-1.30-sig-network

Job object manifests are dumped as expected https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/12945/pull-kubevirt-e2e-k8s-1.30-sig-network/1839333778783211520 PR is ready for review