STOR-3090: Enable pod-delete-after-umount CSI suite for driver OCP manifests - #596
STOR-3090: Enable pod-delete-after-umount CSI suite for driver OCP manifests#596radeore wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@radeore: This pull request references STOR-3090 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 sub-task to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (10)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe five standard CSI driver manifests now enable Merge Risk: ⚪ Minimal · up to OpenShift CSI E2E manifests now use pod deletion after unmount and separate standard from long LUN stress execution. The supplied configuration review identifies no remaining merge-readiness risk. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (10 skipped: 10 unsupported.) Full details: Stable And Deterministic Test NamesExplanation PASS: The pull request changes only ten static YAML manifests. The diff adds driver names, the boolean Full details: Test Structure And QualityExplanation PASS — The pull request changes only ten YAML manifests; it does not add or modify any Ginkgo Full details: Microshift Test CompatibilityExplanation PASS: The pull request changes only 10 YAML manifests. The diff adds no Ginkgo test declarations, test bodies, OpenShift API references, namespaces, or unsupported feature assumptions. Therefore, the MicroShift Test Compatibility check is not applicable. Full details: Single Node Openshift (Sno) Test CompatibilityExplanation PASS — The pull request changes only ten YAML manifests. The diff adds no Ginkgo test declarations or test source files, and the changed files contain no Full details: Topology-Aware Scheduling CompatibilityExplanation PASS: The commit changes only ten CSI test configuration YAML files. The added and modified fields are Full details: Ote Binary Stdout ContractExplanation PASS: The pull request changes only 10 YAML manifest files. It adds Full details: Ipv6 And Disconnected Network Test CompatibilityExplanation PASS: The pull request changes only ten YAML manifests. It adds no Ginkgo declarations or test code. The added values contain driver names, capability flags, pod counts, and timeouts only. No hardcoded IPv4 addresses, URLs, public hostnames, or download commands appear in the changed files. The compatibility check is therefore not applicable. Full details: No-Weak-CryptoExplanation The pull request changes only ten OpenShift YAML manifests. The added and modified lines contain driver names, Full details: Container-PrivilegesExplanation The pull request changes only OpenShift CSI test configuration files. Each changed file contains Full details: No-Sensitive-Data-In-LogsExplanation PASS: The pull request changes only ten YAML manifests. The added values are CSI driver identifiers, the boolean ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/retest-required |
|
/retest-required |
|
@radeore: This pull request references STOR-3090 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 sub-task to target the "5.1.0" version, but no target version was set. DetailsIn response to this:
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. |
|
@jsafrane: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/973e69c0-a1f7-11f1-805a-811a332893ff-0 |
|
@jsafrane: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d304b0c0-a21c-11f1-8167-dd6435b48ba4-0 |
|
@jsafrane: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fc29a370-a550-11f1-80da-92cfff8f0c5a-0 |
|
@jsafrane: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/58448630-a5dc-11f1-82dc-78c295b79a75-0 |
|
/lgtm |
|
Scheduling required tests: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, radeore The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@jsafrane: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0a8eb270-a6c8-11f1-849f-a15404698a96-0 |
|
/override ci/prow/e2e-gcp |
|
@jsafrane: Overrode contexts on behalf of jsafrane: ci/prow/e2e-gcp DetailsIn response to this:
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. |
|
/jira refresh |
|
@radeore: This pull request references STOR-3090 which is a valid jira issue. DetailsIn response to this:
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. |
|
/lgtm cancel |
|
@radeore: This PR was included in a payload test run from openshift/origin#31488
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/34655960-a7c1-11f1-97c7-0aaf55e75feb-0 |
|
/retest-required |
1 similar comment
|
/retest-required |
|
@radeore: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Summary
Enable the OpenShift CSI Pod delete after umount test suite for AWS EBS, AWS EFS, Azure Disk, Azure File, and GCP PD by adding podDeleteAfterUmount: true to each driver's ocp-manifest.yaml.
Split OpenShift-specific CSI test manifests into standard and long variants for AWS EBS, AWS EFS, Azure Disk, Azure File, and GCP PD.
ocp-manifest.yaml — standard jobs: enables podDeleteAfterUmount and disables LUN stress (PodsTotal: 0)
ocp-manifest-long.yaml — long certification jobs: retains existing LUN stress settings (driver-specific PodsTotal / Timeout)
This aligns with openshift/origin#31488, which gates the Pod delete after umount suite via Capabilities.podDeleteAfterUmount in the OpenShift CSI manifest (TEST_OCP_CSI_DRIVER_FILES).
Upstream manifest.yaml files are unchanged.
Adds capability
podDeleteAfterUmount: trueto OpenShift CSI driver ocp-manifests: