arm64: Update arm64 lanes to use the newer kind-1.31 cluster provider

[brianmcarey]

What this PR does / why we need it:

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 #

Special notes for your reviewer:

/cc @dhiller @zhlhahaha @lyarwood

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

[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 brianmcarey. 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:

• github/ci/prow-deploy/files/jobs/kubevirt/common-instancetypes/OWNERS
• github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/OWNERS

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

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-kubevirt-conformance-arm64
rehearsal-pull-kubevirt-e2e-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[zhlhahaha]

Hi Brian, I will try to fix kubevirt/kubevirt#13501 first, then verify the PR.

[zhlhahaha]

• verfiy pull-kubevirt-e2e-arm64 on kind-1.31

Ran 102 of 1409 Specs in 4086.207 seconds
SUCCESS! -- 102 Passed | 0 Failed | 3 Pending | 1304 Skipped
PASS

• verify pull-kubevirt-conformance-arm64 on kind-1.31

Ran 16 of 1409 Specs in 2136.016 seconds
SUCCESS! -- 16 Passed | 0 Failed | 3 Pending | 1390 Skipped
PASS

• verify parallel running e2e tests on kind-1.31
  Parallelly run 3 e2e tests, and all tests pass.

[zhlhahaha]

Hi @brianmcarey , it works fine on my local environment. I have list the tests I done in the previous comment.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-kubevirt-e2e-arm64
rehearsal-pull-kubevirt-conformance-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

@0xFelix @lyarwood I am trying to bump the kind clusters used for the arm builds in common-instancetypes - it looks like it fails on a cleanup from common-instancetypes?
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/3827/rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64/1869352353950339072

[0xFelix]

Not sure that'll make a difference but can you rebase on main to see if the latest changes to the golang version and the builder image help in any way?

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-kubevirt-e2e-arm64
rehearsal-pull-kubevirt-conformance-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[kubevirt-bot]

@brianmcarey: 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
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64	34f89a0	link	unknown	/test pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64	34f89a0	link	unknown	/test pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64	34f89a0	link	unknown	/test pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64	34f89a0	link	unknown	/test pull-common-instancetypes-kubevirt-functest-fedora-arm64
pull-project-infra-lint	34f89a0	link	true	/test pull-project-infra-lint

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.

[lyarwood]

/rehearse rehearsal-pull-kubevirt-e2e-arm64

[kubevirt-bot]

⚠️ @lyarwood you need to be an approver for all the files to run rehearsal.

@vladikr can help run the rehearsal.

If that doesn't work, ping someone from this list:

• dhiller
• phoracek
• rmohr
• vladikr
• xpivarc
• aglitke
• brianmcarey
• davidvossel
• enp0s3
• tiraboschi

[lyarwood]

@brianmcarey this looks like a failure within kubevirtci tbh, I'd like to see rehearsal-pull-kubevirt-e2e-arm64 run if you could trigger the run?

[kubevirt-bot]

Rehearsal jobs created for this PR:

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/rehearse pull-kubevirt-e2e-arm64

The reporting is currently not turned on for the arm64 e2e lanes as there are a couple of known test failures but heres the link to the rehearsal.
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/3827/rehearsal-pull-kubevirt-e2e-arm64/1869756173444452352

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[lyarwood]

/rehearse pull-kubevirt-e2e-arm64

The reporting is currently not turned on for the arm64 e2e lanes as there are a couple of known test failures but heres the link to the rehearsal. https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/3827/rehearsal-pull-kubevirt-e2e-arm64/1869756173444452352

Interesting, that deploys at least. I'll look more in the morning, thanks!

[zhlhahaha]

/rehearse pull-kubevirt-e2e-arm64

The reporting is currently not turned on for the arm64 e2e lanes as there are a couple of known test failures but heres the link to the rehearsal. https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/3827/rehearsal-pull-kubevirt-e2e-arm64/1869756173444452352

The fix for one of the failures (the softboot test) is still under discussion. Other failures stem from new patches and have only appeared since yesterday. I need to investigate these issues further.

You can compare the rehearsal test reports between December 18 and December 19

[zhlhahaha]

Hi, @brianmcarey @lyarwood, I have submitted a PR to use the decorator to mark arm64 related tests. We may wait for that PR get merged. kubevirt/kubevirt#13578