[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]should update kubevirt [release-blocker][test_id:3145]from previous release to target tested release by patching KubeVirt CR

Note: this is different from the regular issues since there is a timeout while trying to create a snapshot:

{{
{ Failure tests/operator_test.go:1908
Unexpected error:
<*errors.errorString | 0xc00028e930>:

{ s: "command failed: cannot run command \"/home/prow/go/src/github.com/kubevirt/kubevirt/_ci-configs/k8s-1.25/.kubectl -n kubevirt-test-default1 create -f /tmp/ginkgo3788155434/vm-v1-snapshot-v1alpha1.yaml --cache-dir /tmp/ginkgo3788155434/oldclient\": exit status 1", }

command failed: cannot run command "/home/prow/go/src/github.com/kubevirt/kubevirt/_ci-configs/k8s-1.25/.kubectl -n kubevirt-test-default1 create -f /tmp/ginkgo3788155434/vm-v1-snapshot-v1alpha1.yaml --cache-dir /tmp/ginkgo3788155434/oldclient": exit status 1
occurred
tests/operator_test.go:1712}
}}
 
As the assignee, review the issue and decide on one of the following actions:

• The flake is a critical bug -> Fix the bug immediately, move this issue to in "In Progress", and keep it open until the testcase does not fail anymore
• The flake is non-critical -> Quarantine it (assigning [QUARANTINE] tag to test name), close this issue, and create a follow up to take the issue out of quarantine
• There was an infrastructure issue (anything "below" the testcase) -> Move the issue to "Obsolete"

Source: https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2022-12-12-024h.html#row33