OCPBUGS-100045: Add openshift/disruptive-longrunning testsuite in release-4.19

[Chandan9112]

Cherry-pick of #31334 (release-4.20) to release-4.19

What

Add the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go on the release-4.19 branch, enabling long-running disruptive tests to run on 4.19.

Why

The disruptive-longrunning suite was added to main, release-4.21, and release-4.20 but is missing in release-4.19. Adding it allows payload jobs to run long-running disruptive tests on 4.19 nightly builds.

Implementation Note

The suite definition uses the Matches function pattern (4.19 style) instead of Qualifiers string slices (4.20+ style), as the TestSuite struct in release-4.19 does not have the Qualifiers field. The matching logic is functionally identical.

Changes

• pkg/testsuites/standard_suites.go: Added openshift/disruptive-longrunning suite definition with:
  • Serial execution (Parallelism: 1)
  • 40-minute test timeout
  • Disruptive cluster stability setting
  • Matches tests containing [Suite:openshift/disruptive-longrunning

Related PRs

Release	Origin PR	Release PR	Jira
main	#30648	—	—
4.21	#30976	#77488	OCPBUGS-81638
4.20	#31334	#80958	OCPBUGS-91996
4.19	This PR	TBD	OCPBUGS-100045

Verification

• go build ./pkg/testsuites/... passes
• gofmt clean
• go generate produces no diff (no tests tagged with this suite in 4.19 yet)

[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: Pro Plus

Run ID: c2085882-24a3-4da9-bc1d-9993b201da5a

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-100045, 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.19.z) matches configured target version for branch (4.19.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-91996 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-91996 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
• bug has dependents

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

Details

In response to this:

Cherry-pick of #31334 (release-4.20) to release-4.19

What

Add the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go on the release-4.19 branch, enabling long-running disruptive tests to run on 4.19.

Why

The disruptive-longrunning suite was added to main, release-4.21, and release-4.20 but is missing in release-4.19. Adding it allows payload jobs to run long-running disruptive tests on 4.19 nightly builds.

Implementation Note

The suite definition uses the Matches function pattern (4.19 style) instead of Qualifiers string slices (4.20+ style), as the TestSuite struct in release-4.19 does not have the Qualifiers field. The matching logic is functionally identical.

Changes

• pkg/testsuites/standard_suites.go: Added openshift/disruptive-longrunning suite definition with:
• Serial execution (Parallelism: 1)
• 40-minute test timeout
• Disruptive cluster stability setting
• Matches tests containing [Suite:openshift/disruptive-longrunning

Related PRs

Release	Origin PR	Release PR	Jira
main	#30648	—	—
4.21	#30976	#77488	OCPBUGS-81638
4.20	#31334	#80958	OCPBUGS-91996
4.19	This PR	TBD	OCPBUGS-100045

Verification

• go build ./pkg/testsuites/... passes
• gofmt clean
• go generate produces no diff (no tests tagged with this suite in 4.19 yet)

/cc @rphillips @bhargaviravindranath

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.

[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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Chandan9112
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme 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

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.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-91996 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-91996 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
• bug has dependents

Details

In response to this:

Cherry-pick of #31334 (release-4.20) to release-4.19

What

Add the openshift/disruptive-longrunning test suite definition to pkg/testsuites/standard_suites.go on the release-4.19 branch, enabling long-running disruptive tests to run on 4.19.

Why

The disruptive-longrunning suite was added to main, release-4.21, and release-4.20 but is missing in release-4.19. Adding it allows payload jobs to run long-running disruptive tests on 4.19 nightly builds.

Implementation Note

The suite definition uses the Matches function pattern (4.19 style) instead of Qualifiers string slices (4.20+ style), as the TestSuite struct in release-4.19 does not have the Qualifiers field. The matching logic is functionally identical.

Changes

• pkg/testsuites/standard_suites.go: Added openshift/disruptive-longrunning suite definition with:
• Serial execution (Parallelism: 1)
• 40-minute test timeout
• Disruptive cluster stability setting
• Matches tests containing [Suite:openshift/disruptive-longrunning

Related PRs

Release	Origin PR	Release PR	Jira
main	#30648	—	—
4.21	#30976	#77488	OCPBUGS-81638
4.20	#31334	#80958	OCPBUGS-91996
4.19	This PR	TBD	OCPBUGS-100045

Verification

• go build ./pkg/testsuites/... passes
• gofmt clean
• go generate produces no diff (no tests tagged with this suite in 4.19 yet)

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.