ROSAENG-64530: add weekly full lifecycle CAPA e2e job

[andclt]

Summary

• Adds a weekly capa-e2e-full periodic job that runs the complete ROSA HCP lifecycle: provision → upgrade control plane → upgrade machine pool → add machinepool → delete machinepool → delete cluster
• Passes RESERVE_UPGRADE_PATH=true so the test provisions with a version that has available upgrades (e.g. 4.22.6 instead of 4.22.7), ensuring upgrade suites have a target version

Summary by CodeRabbit

• Adds a weekly capa-e2e-full job for the OpenShift Online ROSA HCP CI.
• Runs the full cluster lifecycle test, including provisioning, upgrades, machine pool changes, and deletion.
• Sets RESERVE_UPGRADE_PATH=true so provisioning selects a version with an available upgrade target.
• Uses the stable 4.22 channel and an eight-hour timeout.

[openshift-ci-robot]

@andclt: This pull request references ROSAENG-64530 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.

Details

In response to this:

Summary

• Adds a weekly capa-e2e-full periodic job that runs the complete ROSA HCP lifecycle: provision → upgrade control plane → upgrade machine pool → add machinepool → delete machinepool → delete cluster
• Passes RESERVE_UPGRADE_PATH=true so the test provisions with a version that has available upgrades (e.g. 4.22.6 instead of 4.22.7), ensuring upgrade suites have a target version

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

[coderabbitai]

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

Run ID: f3d93b14-b234-455b-aafd-58cea8256c27

📥 Commits

Reviewing files that changed from the base of the PR and between 4059300 and c70ff26.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main_capa-e2e-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (3)

• ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main_capa-e2e.yaml
• ci-operator/step-registry/rosa/e2e/capa/rosa-e2e-capa-commands.sh
• ci-operator/step-registry/rosa/e2e/capa/rosa-e2e-capa-ref.yaml

---

Walkthrough

The CAPA E2E workflow now supports optional upgrade-path reservation. A weekly full-suite run uses the stable 4.22 channel, reserves upgrade paths, and has an eight-hour timeout.

Changes

CAPA E2E upgrade-path testing

Layer / File(s)	Summary
Reserve upgrade-path control ci-operator/step-registry/rosa/e2e/capa/rosa-e2e-capa-ref.yaml, ci-operator/step-registry/rosa/e2e/capa/rosa-e2e-capa-commands.sh	The step defines RESERVE_UPGRADE_PATH. When it is true, the command passes reserve_upgrade_path=true to the test suite.
Scheduled full-suite configuration ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main_capa-e2e.yaml	A weekly capa-e2e-full run uses the stable 4.22 channel, full-suite execution, reserved upgrade paths, and an eight-hour timeout.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• openshift/release#82728: Both changes extend CAPA E2E configuration and propagate provisioning controls through EXTRA_VARS.

Suggested reviewers: serngawy

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding a weekly full lifecycle CAPA end-to-end job.
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	The commit adds CI configuration and variable propagation only; no Ginkgo It, Describe, Context, or When test titles are added or changed.
Test Structure And Quality	✅ Passed	The PR changes only YAML and shell CI wiring; it adds no Ginkgo It blocks, assertions, Eventually calls, or cluster-resource test code.
Microshift Test Compatibility	✅ Passed	The PR adds only a periodic YAML job and shell/step-registry variables; it adds no Ginkgo It, Describe, Context, or When tests, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR adds only CI YAML, a generated periodic job, and a shell wrapper; it adds no Ginkgo tests or test bodies requiring SNO topology review.
Topology-Aware Scheduling Compatibility	✅ Passed	The patch changes CI job configuration and test-suite variable propagation only; it adds no pod affinity, topology spread, replica, node selector, toleration, or PDB scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The commit changes only YAML files and a shell wrapper; it adds no OTE binary or process-level Go suite code that could emit non-JSON stdout.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes CI YAML and shell wiring only. The diff adds no Ginkgo test declarations or new IPv4 or external-connectivity test code.
No-Weak-Crypto	✅ Passed	The added diff contains no MD5, SHA1, DES, 3DES, RC4, Blowfish, or ECB use. The new shell comparison only checks RESERVE_UPGRADE_PATH against "true".
Container-Privileges	✅ Passed	The changed config, generated job, step reference, and script contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds no logging statements or sensitive values. It adds only a boolean test variable and standard secret mounts; credential loading remains protected by set +x.

✨ 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: andclt
Once this PR has been reviewed and has the lgtm label, please assign tiwillia 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-online/rosa-e2e/OWNERS
• ci-operator/jobs/openshift-online/rosa-e2e/OWNERS
• ci-operator/step-registry/rosa/e2e/capa/OWNERS [andclt]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@andclt: 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-online-rosa-e2e-main_capa-e2e-capa-e2e	N/A	periodic	Registry content changed
periodic-ci-openshift-online-rosa-e2e-main_capa-e2e-capa-e2e-full	N/A	periodic	Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.