Since https://github.com/openshift/origin/pull/30305 was mereged, all CSI presubmit jobs are failing with:

Suite run returned error: no tests to runerror: error running a test suite: no tests to run 

Sample from the very PR that broke the jobs: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30305/pull-ci-openshift-origin-main-e2e-gcp-csi/1971353906080387072 

Version-Release number of selected component (if applicable):

4.21.0-0.nightly-2025-10-02-215712 (started few days earlier).

How reproducible:

Always

Steps to Reproduce:

1. Get a cluster on AWS
2. get a CSI driver test manifest, e.g.:

 wget https://raw.githubusercontent.com/openshift/csi-operator/refs/heads/main/test/e2e/aws-ebs/manifest.yaml

1. Run the CSI tests:

TEST_CSI_DRIVER_FILES=manifest.yaml ./openshift-tests run openshift/csi --monitor=machine-lifecycle

Actual results:

Suite run returned error: no tests to run
error: error running a test suite: no tests to run 

Expected results:

More than 280 tests are found.

Additional info:

• Guys, even CI in the PR failed all CSI tests. Should we make them mandatory?
• From some strange reason, periodic tests are green, e.g. https://testgrid.k8s.io/redhat-openshift-ocp-release-4.21-informing#periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-csi . But they still miss all CSI driver tests, there are just synthetic ones running for past few days.