kubevirt: [flaky ci] Creating a VirtualMachineInstance when virt-handler is not responsive [test_id:1634]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4710/pull-kubevirt-e2e-k8s-1.17/1341915356280655873

tests/vmi_lifecycle_test.go:630 Expected <string>: to equal <string>: NodeUnresponsive tests/vmi_lifecycle_test.go:663

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

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

/triage build-watcher