[DO NOT REVIEW] TEST: fail passt test

[iholder101]

PLEASE DO NOT REVIEW.

[kubevirt-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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/test-infra repository.

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from iholder101. For more information see the Kubernetes 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:

• tests/network/OWNERS

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

[iholder101]

/uncc @AlonaKaplan

[iholder101]

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

[kubevirt-bot]

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

Test name	Commit	Details	Required	Rerun command
pull-kubevirt-e2e-k8s-1.29-sig-network	adc5669	link	true	/test pull-kubevirt-e2e-k8s-1.29-sig-network

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/test-infra repository. I understand the commands that are listed here.

[EdDev]

As we suspected, the VMs are scheduled on different nodes:

kubevirt-test-default1   pod/virt-launcher-testvmi-vbdnq-zqdbt                     4/4     Running            0               35s    10.244.196.155   node01   <none>           1/1
kubevirt-test-default1   pod/virt-launcher-testvmi-x4mhf-mm9k9                     4/4     Running            0               70s    10.244.140.121   node02   <none>           1/1

@iholder101 , can you now assert it to fail after the migration check succeeds?
I would expect them both to run on the same node.