e2e, arm64: make the e2e tests works of Arm64 platform

[zhlhahaha]

What this PR does / why we need it:
Enable e2e test works on Arm64 platform.

1. Make cluster-sync work on kind provider
2. Disable VDDK deployment on Arm64
3. Label VDDK e2e tests, thus we can skip them
4. Fix several e2e tests

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3466

Release note:

None

[coveralls]

coverage: 59.426% (+0.01%) from 59.412%
when pulling 9478ffd on zhlhahaha:3466
into f4cbf29 on kubevirt:main.

[zhlhahaha]

To make the it works, relay on

• cluster-up, kind: all to exec command via ssh.sh and add port mapping for kind cluster kubevirtci#1344
• Multiarch fakeovirt-image #3519

[zhlhahaha]

cc: @awels @cfilleke @xpivarc @dhiller

[zhlhahaha]

The e2e tests have fully passed in a docker in docker environment by running

export TARGET=kind-1.28
export RANDOM_CR=true
export KUBEVIRT_STORAGE=hpp
export HPP_CLASSIC=true
export CDI_E2E_SKIP="Destructive|\[VDDK\]"
./automation/test.sh

[zhlhahaha]

If this PR get merged, we can add a periodic e2e tests for CDI on Arm64 cluster.

[akalenyu]

Thank you for this great effort! questions attached

[zhlhahaha]

@akalenyu Thanks for your quick comment! I do not have time you reply all your comment today and I will reply you tomorrow.

[zhlhahaha]

@akalenyu Some background, I verify the cdi e2e tests in a prow pods on Arm64 server which is similar to the kubeVirt Community CI/CD environment.
The host system is ubuntu.

[akalenyu]

@akalenyu Thanks for your quick comment! I do not have time you reply all your comment today and I will reply you tomorrow.

@akalenyu Some background, I verify the cdi e2e tests in a prow pods on Arm64 server which is similar to the kubeVirt Community CI/CD environment. The host system is ubuntu.

Totally understandable, I am out tomorrow but I can pick up on it next week. Feel free to ping on the k8s slack if you need any help.

[akalenyu]

/test pull-cdi-goveralls
/test pull-cdi-unit-test
not related

[akalenyu]

/test pull-cdi-unit-test

[akalenyu]

/test pull-containerized-data-importer-e2e-istio

[zhlhahaha]

/retest

[zhlhahaha]

/retest

[akalenyu]

I am not sure why all lanes fail with CDI pods not being ready

timed out waiting for the condition on pods/cdi-docker-registry-host-7989bdb8c8-8djb2
timed out waiting for the condition on pods/cdi-file-host-5c87dc856f-6rpqg
timed out waiting for the condition on pods/cdi-operator-59c7548cfb-g76fj
timed out waiting for the condition on pods/cdi-uploadproxy-6548888c56-9vwtr

/test pull-containerized-data-importer-e2e-nfs

EDIT: I think the non-registry pods didn't really fail the check, their state just didn't get evaluated since docker-registry host was broken or something like that

[zhlhahaha]

@akalenyu
We also need Multiarch fakeovirt-image.
#3519

I have write a script to build multiarch fakeovirt-image(#3519 (comment)), but need someone run it and publish it to the quay.io/kubevirt/fakeovirt

[akalenyu]

@akalenyu We also need Multiarch fakeovirt-image. #3519

I have write a script to build multiarch fakeovirt-image(#3519 (comment)), but need someone run it and publish it to the quay.io/kubevirt/fakeovirt

I see that @awels is on board so maybe @dhiller can help push this

[akalenyu]

/approve
anything else needed? can this merge without the image push?

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akalenyu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [akalenyu]

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

[kubevirt-bot]

@zhlhahaha: 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-containerized-data-importer-e2e-ceph-wffc	4881c70	link	true	/test pull-containerized-data-importer-e2e-ceph-wffc

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.

[zhlhahaha]

anything else needed? can this merge without the image push?

Yes, we need a multi-architecture quay.io/kubevirt/fakeovirt image to enable us to run periodic e2e tests on Arm.

Currently, I’m working on two tasks:

1. Writing a multi-architecture manifest build script for CDI, similar to the approach used in kubevirt/kubevirt. Once this is completed, we’ll be able to publish multi-architecture CDI images.
2. Coordinating with my company to contribute an Arm64 server for the CDI CI/CD pipeline. This will allow us to integrate Arm64-related e2e and unit tests into the PR submission process.