kubevirt, hs, aws: Fail if live migraion fails

[qinqon]

At aws the hypershift kubevirt live migration test check if the node goes from ready to not ready during live migration (that means live feature is broken) to check partially the live migration feature.

This change remove that check and ensure the test fail, since nodes moving to not ready is not an option.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: qinqon
Once this PR has been reviewed and has the lgtm label, please assign nunnatsa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• test/extended/kubevirt/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@qinqon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agnostic-ovn-cmd	5e5bcff	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-baremetalds-kubevirt	5e5bcff	link	false	/test e2e-baremetalds-kubevirt
ci/prow/e2e-aws-ovn-kubevirt	5e5bcff	link	false	/test e2e-aws-ovn-kubevirt
ci/prow/e2e-hypershift-conformance	5e5bcff	link	false	/test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-single-node-serial	5e5bcff	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	5e5bcff	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/okd-scos-e2e-aws-ovn	5e5bcff	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node	5e5bcff	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-upgrade	5e5bcff	link	false	/test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.