NO-ISSUE: Added periodic job for longrunning testsuite for 4.20

[Chandan9112]

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing.
The test suite was added in openshift/origin#31334

This is a cherry-pick of #77488 (by @BhargaviGudi for 4.21), adapted for the 4.20 nightly payload.

What this PR does

Adds the e2e-aws-disruptive-longrunning periodic job to openshift-release-main__nightly-4.20.yaml and the corresponding generated job definition in openshift-release-main-periodics.yaml.

The job:

• Runs daily at 12:00 UTC (cron: 0 12 * * *)
• Uses the openshift-org-aws cluster profile with SSH enabled
• Executes the openshift/disruptive-longrunning test suite
• Uses the openshift-e2e-aws-disruption workflow
• Includes observers-resource-watch for monitoring
• Is configured as informing (not blocking)

How to trigger manually

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

Reference PRs

Version	PR	Author	Status
4.21 (CI job)	#77488	@BhargaviGudi	Merged

Related PRs (suite definition in openshift/origin)

Branch	PR	Status
main	openshift/origin#30648	Merged
release-4.21	openshift/origin#30976	Merged
release-4.20	openshift/origin#31334	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 openshift/origin#31334, but that PR depends on merging this 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

[coderabbitai]

Walkthrough

A new nightly test job e2e-aws-disruptive-longrunning is added to the OpenShift 4.20 nightly CI config. It runs daily at noon UTC using the openshift-org-aws cluster profile, the openshift/disruptive-longrunning test suite, SSH enabled, observers-resource-watch active, and the openshift-e2e-aws-disruption workflow.

Changes

Add e2e-aws-disruptive-longrunning nightly job

Layer / File(s)	Summary
New nightly test job definition ci-operator/config/openshift/release/openshift-release-main__nightly-4.20.yaml	Adds e2e-aws-disruptive-longrunning to the tests list with a 0 12 * * * cron, openshift-org-aws cluster profile, TEST_REQUIRES_SSH: "yes", TEST_SUITE: openshift/disruptive-longrunning, TEST_TYPE: suite, observers-resource-watch enabled, and the openshift-e2e-aws-disruption workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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 only adds a CI job stanza in YAML; no Ginkgo titles or dynamic test-name strings were added.
Test Structure And Quality	✅ Passed	PR only adds a ci-operator periodic job YAML; no Ginkgo test code or assertions were modified, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only adds a periodic ci-operator job YAML; no new Ginkgo tests or test bodies were introduced to assess for MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only adds a periodic ci-operator job; no new Ginkgo tests or code paths were introduced to assess for SNO assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	PASS: PR only adds a ci-operator periodic test job; no deployment manifests, operators, controllers, or pod scheduling constraints were changed.
Ote Binary Stdout Contract	✅ Passed	PR only adds a ci-operator periodic job YAML; no OTE binary code or process-level stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only adds a ci-operator periodic job mirroring the existing 4.21 entry; no Ginkgo test code or network assumptions were introduced.
No-Weak-Crypto	✅ Passed	Only a CI YAML job was added; the diff and target file contain no weak-crypto terms or custom crypto/comparison code.
Container-Privileges	✅ Passed	Added job stanza only sets cron, cluster profile, env, observers, and workflow; no privileged/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPrivilegeEscalation fields appear.
No-Sensitive-Data-In-Logs	✅ Passed	PASS: The added job block only sets cron, cluster_profile, env vars, observers, and workflow; no secrets, PII, or hostnames are introduced.
Title check	✅ Passed	The title accurately summarizes the main change: adding a periodic longrunning test job for 4.20.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

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

[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 smg247 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:

• ci-operator/config/openshift/release/OWNERS
• ci-operator/jobs/openshift/release/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 explicitly references no jira issue.

Details

In response to this:

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing.
The test suite was added in openshift/origin#31334

This is a cherry-pick of #77488 (by @BhargaviGudi for 4.21), adapted for the 4.20 nightly payload.

What this PR does

Adds the e2e-aws-disruptive-longrunning periodic job to openshift-release-main__nightly-4.20.yaml and the corresponding generated job definition in openshift-release-main-periodics.yaml.

The job:

• Runs daily at 12:00 UTC (cron: 0 12 * * *)
• Uses the openshift-org-aws cluster profile with SSH enabled
• Executes the openshift/disruptive-longrunning test suite
• Uses the openshift-e2e-aws-disruption workflow
• Includes observers-resource-watch for monitoring
• Is configured as informing (not blocking)

How to trigger manually

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

Reference PRs

Version	PR	Author	Status
4.21 (CI job)	#77488	@BhargaviGudi	Merged
4.20 (CI job)	This PR	@Chandan9112	Draft

Related PRs (suite definition in openshift/origin)

Branch	PR	Status
main	openshift/origin#30648	Merged
release-4.21	openshift/origin#30976	Merged
release-4.20	openshift/origin#31334 (OCPBUGS-91996)	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 openshift/origin#31334, but that PR depends on merging this 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-merge-bot]

[REHEARSALNOTIFIER]
@Chandan9112: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning	N/A	periodic	Periodic changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[Chandan9112]

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning

[openshift-merge-bot]

@Chandan9112: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@Chandan9112: 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/rehearse/periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning	c7b0b5a	link	unknown	/pj-rehearse periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-disruptive-longrunning
ci/prow/generated-config	c7b0b5a	link	true	/test generated-config

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.