Skip to content

OCPBUGS-42363: Re-enable Azure Disk load test#558

Open
jsafrane wants to merge 1 commit into
openshift:mainfrom
jsafrane:reenable-azure-disk-load
Open

OCPBUGS-42363: Re-enable Azure Disk load test#558
jsafrane wants to merge 1 commit into
openshift:mainfrom
jsafrane:reenable-azure-disk-load

Conversation

@jsafrane
Copy link
Copy Markdown
Contributor

In Nov 2024 Microsoft wrote that they're deploying a fix for OCPBUGS-42363 in 2025. It's mid 2026, let's try to enable the test.

In Nov 2024 Microsoft wrote that they're deploying a fix for OCPBUGS-42363
in 2025. It's mid 2026, let's try to enable the test.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@jsafrane: This pull request references Jira Issue OCPBUGS-42363, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

In Nov 2024 Microsoft wrote that they're deploying a fix for OCPBUGS-42363 in 2025. It's mid 2026, let's try to enable the test.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 27, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

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: 723f1a1e-8795-4158-955f-891ef28b6037

📥 Commits

Reviewing files that changed from the base of the PR and between 5027bfc and 1c4d8f5.

📒 Files selected for processing (1)
  • test/e2e/azure-disk/ocp-manifest.yaml

📝 Walkthrough

Walkthrough

This pull request increases the pod count in the Azure disk CSI end-to-end test manifest. The LUNStressTest.PodsTotal configuration parameter in test/e2e/azure-disk/ocp-manifest.yaml is updated from 10 to 260, which scales up the number of pods participating in the disk stress test to exercise a larger workload during testing.

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly references OCPBUGS-42363 and indicates the main change is re-enabling the Azure Disk load test, which aligns with the configuration update in the manifest.
Description check ✅ Passed The description provides context for re-enabling the Azure Disk load test, relating to a Microsoft fix announced in Nov 2024 for OCPBUGS-42363, which is directly relevant to 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 PR modifies only YAML manifest configuration files (16 files), not Go test code. No Ginkgo test definitions or test names present to evaluate against the check.
Test Structure And Quality ✅ Passed PR modifies only a YAML manifest configuration file, not Ginkgo test code. The custom check for Ginkgo test quality is not applicable to configuration files.
Microshift Test Compatibility ✅ Passed No new Ginkgo tests are added in this PR. The change only modifies a YAML manifest configuration file (PodsTotal parameter), not test code, so the MicroShift Test Compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies only a YAML test configuration file (ocp-manifest.yaml), not adding new Ginkgo test definitions. The check applies only when new Ginkgo tests are added.
Topology-Aware Scheduling Compatibility ✅ Passed The change modifies a test configuration file only. It increases a test parameter (PodsTotal) from 10 to 260. No scheduling constraints, affinity rules, or topological assumptions are introduced.
Ote Binary Stdout Contract ✅ Passed PR changes only a YAML manifest configuration file (test/e2e/azure-disk/ocp-manifest.yaml), not executable test code. No OTE binary stdout violations are applicable to YAML data files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds only YAML configuration files, not new Ginkgo e2e tests. Check applies only to new Go test definitions; therefore not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from RomanBednar and gnufied May 27, 2026 11:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2026
@jsafrane
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 28, 2026

@jsafrane: all tests passed!

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.

@jsafrane
Copy link
Copy Markdown
Contributor Author

/test e2e-azure-csi

@jsafrane
Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-azure-csi

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 29, 2026

@jsafrane: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-azure-csi

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/43867480-5b5c-11f1-9829-bdd2f5c76866-0

@jsafrane
Copy link
Copy Markdown
Contributor Author

/test help

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 29, 2026

@jsafrane: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test aws-efs-operator-e2e
/test aws-efs-single-zone-cross-account-operator-e2e
/test aws-efs-single-zone-operator-e2e
/test ci-index-aws-efs-csi-driver-operator-bundle
/test ci-index-smb-csi-driver-operator-bundle
/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-openstack-cinder-csi
/test e2e-openstack-manila-csi
/test hypershift-aws-e2e-external
/test hypershift-e2e-openstack-aws-csi-cinder
/test hypershift-e2e-openstack-aws-csi-manila
/test images
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test aws-efs-cross-account-operator-e2e
/test aws-efs-operator-e2e-extended
/test aws-efs-single-zone-operator-e2e-extended
/test aws-efs-sts-cross-account-operator-e2e
/test e2e-aws-csi-extended
/test e2e-aws-eusc-techpreview-csi
/test e2e-azure-csi-extended
/test e2e-azure-csi-hypershift
/test e2e-azure-csi-volumeattributesclass
/test e2e-azure-file-csi-extended
/test e2e-azure-file-csi-hypershift
/test e2e-azure-file-nfs-csi-hypershift
/test e2e-azure-manual-oidc
/test e2e-azurestack-csi
/test e2e-openstack
/test hypershift-e2e-aks
/test okd-scos-e2e-aws-ovn
/test security
/test smb-operator-e2e
/test smb-operator-e2e-extended
/test smb-win2019-operator-e2e
/test smb-win2022-operator-e2e

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-csi-operator-main-aws-efs-operator-e2e
pull-ci-openshift-csi-operator-main-ci-index-aws-efs-csi-driver-operator-bundle
pull-ci-openshift-csi-operator-main-ci-index-smb-csi-driver-operator-bundle
pull-ci-openshift-csi-operator-main-e2e-aws-csi
pull-ci-openshift-csi-operator-main-e2e-aws-ovn-upgrade
pull-ci-openshift-csi-operator-main-e2e-azure
pull-ci-openshift-csi-operator-main-e2e-azure-csi
pull-ci-openshift-csi-operator-main-e2e-azure-file-csi
pull-ci-openshift-csi-operator-main-e2e-azure-file-nfs-csi
pull-ci-openshift-csi-operator-main-e2e-azure-ovn-upgrade
pull-ci-openshift-csi-operator-main-hypershift-aws-e2e-external
pull-ci-openshift-csi-operator-main-hypershift-e2e-aks
pull-ci-openshift-csi-operator-main-images
pull-ci-openshift-csi-operator-main-okd-scos-images
pull-ci-openshift-csi-operator-main-security
pull-ci-openshift-csi-operator-main-unit
pull-ci-openshift-csi-operator-main-verify
pull-ci-openshift-csi-operator-main-verify-deps
Details

In response to this:

/test help

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants