OCPBUGS-91996: Add openshift/disruptive-longrunning testsuite in release-4.20 branch

[Chandan9112]

Add openshift/disruptive-longrunning testsuite in release-4.20 branch

Manual cherry-pick of #30976 (by @BhargaviGudi) to release-4.20.

The automatic /cherry-pick release-4.20 failed due to a merge conflict in pkg/testsuites/standard_suites.go (different file structure between release-4.21 and release-4.20). This PR manually applies the same change.

What this PR does

Adds the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go and a README with usage instructions in test/extended/node/. This enables long-running disruptive tests (e.g., node reboots, configuration changes, cluster-wide disruptions) to run on the 4.20 release branch.

CI job: openshift/release#80958

The test can be executed only after the CI job is merged.

How to run

To run the entire long-running disruptive test suite on a cluster:

./openshift-tests run "openshift/disruptive-longrunning" --cluster-stability=Disruptive

To trigger via CI:

/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning

Reference PRs

Branch	PR	Author	Status
main	#30648	@BhargaviGudi	Merged
release-4.21	#30976	@BhargaviGudi	Merged
release-4.20	This PR	@Chandan9112	Under Review

Note: pj-rehearse validation will fail because no tests are tagged with this suite yet in release-4.20. Tests are being added via subsequent PRs, but those PRs depend on merging this suite definition and CI job configuration first so the tests have a job to run in.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@Chandan9112: This pull request references Jira Issue OCPBUGS-81638, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• expected dependent Jira Issue OCPBUGS-82197 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

Summary

Manual cherry-pick of #30976 (by @BhargaviGudi) to release-4.20.

The automatic /cherry-pick release-4.20 failed due to a merge conflict in pkg/testsuites/standard_suites.go (different file structure between release-4.21 and release-4.20). This PR manually applies the same change.

What this PR does

Adds the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go, enabling long-running disruptive tests (e.g., node reboots, config changes) to run on the 4.20 release branch via:

/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning

Reference PRs

Branch	PR	Author	Status
main	#30648	@BhargaviGudi	Merged
release-4.21	#30976	@BhargaviGudi	Merged
release-4.20	This PR	@Chandan9112	Draft

Related

• CI job configuration (openshift/release): TBD — will add e2e-aws-disruptive-longrunning to openshift-release-main__nightly-4.20.yaml

Made with Cursor

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 2cadcfd5-bf84-4047-8277-3a06084ec06e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci-robot]

@Chandan9112: This pull request references Jira Issue OCPBUGS-91996, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-91996 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

Summary

Manual cherry-pick of #30976 (by @BhargaviGudi) to release-4.20.

The automatic /cherry-pick release-4.20 failed due to a merge conflict in pkg/testsuites/standard_suites.go (different file structure between release-4.21 and release-4.20). This PR manually applies the same change.

What this PR does

Adds the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go, enabling long-running disruptive tests (e.g., node reboots, config changes) to run on the 4.20 release branch via:

/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning

Reference PRs

Branch	PR	Author	Status
main	#30648	@BhargaviGudi	Merged
release-4.21	#30976	@BhargaviGudi	Merged
release-4.20	This PR	@Chandan9112	Draft

Related

• CI job configuration (openshift/release): TBD — will add e2e-aws-disruptive-longrunning to openshift-release-main__nightly-4.20.yaml

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.

[Chandan9112]

/jira refresh

[openshift-ci-robot]

@Chandan9112: This pull request references Jira Issue OCPBUGS-91996, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-91996 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[Chandan9112]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-81638 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-81638 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

Details

In response to this:

/jira refresh

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]

@Chandan9112: This pull request references Jira Issue OCPBUGS-91996, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-81638 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-81638 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

Details

In response to this:

Add openshift/disruptive-longrunning testsuite in release-4.20 branch

Manual cherry-pick of #30976 (by @BhargaviGudi) to release-4.20.
Related PR: https://github.com/openshift/origin/pull/30648/changes#diff-6f59ac4ffef01ed6ee14ebe27baed2d4eb20e438e60a5a32f42d795ac2683d32

The automatic /cherry-pick release-4.20 failed due to a merge conflict in pkg/testsuites/standard_suites.go (different file structure between release-4.21 and release-4.20). This PR manually applies the same change.

What this PR does

Adds the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go and a README with usage instructions in test/extended/node/. This enables long-running disruptive tests (e.g., node reboots, configuration changes, cluster-wide disruptions) to run on the 4.20 release branch.

The suite is configured with:

• Parallelism: 1 (serial execution)
• TestTimeout: 40 * time.Minute
• ClusterStabilityDuringTest: ginkgo.Disruptive

CI job: openshift/release#80958

The test can be executed only after the CI job is merged.

How to run

To run the entire long-running disruptive test suite on a cluster:

./openshift-tests run "openshift/disruptive-longrunning" --cluster-stability=Disruptive

To trigger via CI:

/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning

Reference PRs

Branch	PR	Author	Status
main	#30648	@BhargaviGudi	Merged
release-4.21	#30976	@BhargaviGudi	Merged
release-4.20	This PR	@Chandan9112	Draft

Note: pj-rehearse validation will fail because no tests are tagged with this suite yet in release-4.20. Tests are being added via subsequent PRs, but those PRs depend on merging this suite definition and CI job configuration first so the tests have a job to run in.

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]

@Chandan9112: 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
ci/prow/e2e-vsphere-ovn	97f2831	link	true	/test e2e-vsphere-ovn

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.

[BhargaviGudi]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BhargaviGudi, Chandan9112
Once this PR has been reviewed and has the lgtm label, please assign xueqzhan for approval. For more information see the Code Review Process.

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

Details

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