STOR-2918: AWS-EBS CI - enable PVC cloning tests

[dfajmon]

Rebase enabled volume copying, enabling CI tests.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@dfajmon: This pull request references STOR-2918 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "5.0.0" version, but multiple target versions were set.

Details

In response to this:

Rebase enabled volume copying, enabling CI tests.

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 openshift-eng/jira-lifecycle-plugin repository.

[dfajmon]

/test ?

[dfajmon]

/pipeline required

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-azure-file-nfs-csi
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-csi
/test e2e-gcp-ovn-upgrade

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfajmon

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dfajmon]

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: d1be37c1-754e-44af-ab9b-54b1c7a04f75

📥 Commits

Reviewing files that changed from the base of the PR and between 0ab2f5a and 5adc580.

📒 Files selected for processing (1)

• test/e2e/aws-ebs/manifest.yaml

---

📝 Walkthrough

Walkthrough

The AWS EBS CSI test manifest now enables the pvcDataSource capability in DriverInfo.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies enabling AWS EBS PVC cloning tests, which matches the primary change.
Description check	✅ Passed	The description relates to enabling volume copying and CI tests, which matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The PR changes only a static YAML capability flag; it adds no Ginkgo test titles or dynamic values.
Test Structure And Quality	✅ Passed	The commit changes only test/e2e/aws-ebs/manifest.yaml; it adds pvcDataSource: true and contains no Ginkgo test code to assess for setup, waits, or assertions.
Microshift Test Compatibility	✅ Passed	The change only adds pvcDataSource: true to the EBS manifest; the parent diff adds no Ginkgo tests or MicroShift-incompatible API usage.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only test/e2e/aws-ebs/manifest.yaml to enable pvcDataSource; it adds no Ginkgo tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The EBS change only sets DriverInfo.Capabilities.pvcDataSource: true in a test manifest; it adds no deployment, replica, affinity, selector, spread, toleration, or PDB constraint.
Ote Binary Stdout Contract	✅ Passed	The PR changes only one YAML capability flag; it adds no Go or process-level code and no stdout-related lines.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The commit only adds pvcDataSource: true to the EBS manifest; it adds no Ginkgo tests or networking and external-connectivity assumptions.
No-Weak-Crypto	✅ Passed	The commit changes only the EBS YAML manifest by adding pvcDataSource: true; no weak-crypto or secret-comparison indicators appear.
Container-Privileges	✅ Passed	The commit changes only pvcDataSource: true; AWS EBS manifests contain no privileged, host namespace, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The only added line is pvcDataSource: true in a test manifest; the commit adds no logging or sensitive-data output.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[jsafrane]

/retest

[openshift-ci]

@dfajmon: 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
ci/prow/hypershift-e2e-aks	5adc580	link	false	/test hypershift-e2e-aks
ci/prow/security	5adc580	link	false	/test security
ci/prow/e2e-aws-csi	5adc580	link	true	/test e2e-aws-csi

Full PR test history. Your PR dashboard.

Details

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.