Update tests to use 2025.1 openstack, disable zswap

[zetaab]

What this PR does / why we need it:

Which issue this PR fixes(if applicable):
fixes #

Special notes for reviewers:

Release note:

NONE

[k8s-ci-robot]

[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 assign zetaab 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:

• OWNERS

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

[mnaser]

FYI I think there is work happening here => #2888

[zetaab]

yep but the problem is that none of the csi tests are working. I am trying to find out why

[zetaab]

/test openstack-cloud-csi-cinder-e2e-test

[zetaab]

/test openstack-cloud-csi-cinder-e2e-test

[k8s-ci-robot]

@zetaab: 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
openstack-cloud-csi-cinder-e2e-test	1e0d873	link	true	/test openstack-cloud-csi-cinder-e2e-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[k8s-ci-robot]

PR needs rebase.

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.

[zetaab]

@stephenfin & @kayrus I executed the tests manually and the result was success. However, the tests takes like 2.5 hours. No idea why this CI is failing

[stephenfin]

I've tested locally on both Bobcat and Dalmatian. I see the same performance regression on the latter that we're seeing CI. Something here is definitely off. It doesn't appear to be service related so far, however, as I've updated all 6 running services to Dalmatian (including applying DB schema and data migrations) and there's no performance change 😕 I'll keep investigating next week