MULTIARCH-6023: Update ibm power single-node-openshift scheduling

[mpkredhat]

Aim is to improve MultiArch Power CI performance.
Removing jobs for Single Node Operator specific to 4.15,4.16,4.17 and adding jobs for 4.22/4.23.

Summary by CodeRabbit

This PR updates the CI scheduling configuration for IBM Power single-node-openshift deployments to improve MultiArch Power CI performance. The changes involve removing SNO (Single Node Operator) test job definitions from older OpenShift release branches and adding them to newer branches.

Changes made:

• OpenShift 4.14, 4.15, 4.16: Removed the ocp-e2e-sno-power and ocp-e2e-agent-sno-power test jobs for IBM Power systems, with 4.15 also removing the ocp-assisted-sno-power job (3 jobs total removed from 4.15). These represent the discontinuation of SNO testing for older release branches.
• OpenShift 4.22: Added two new SNO test jobs for IBM Power systems:
  • ocp-e2e-sno-power (UPI installation type)
  • ocp-e2e-agent-sno-power (agent installation type)

These jobs are configured to target powervs-1 infrastructure and run on defined cron schedules. The changes reflect a shift in testing focus from maintenance branches (4.15, 4.16) to more recent stable releases (4.22).

The PR addresses JIRA issue MULTIARCH-6023 and focuses the Power architecture CI testing effort on supported OpenShift versions.

[openshift-ci-robot]

@mpkredhat: This pull request references MULTIARCH-6023 which is a valid jira issue.

Details

In response to this:

Aim is to improve MultiArch Power CI performance.
Removing jobs for Single Node Operator specific to 4.15,4.16,4.17 and adding jobs for 4.22/4.23.

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]

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: 78af775e-a44b-4b1a-8a54-c27177c739c0

📥 Commits

Reviewing files that changed from the base of the PR and between 37eebc5 and 24d5ebd.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (4)

• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.14.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.15.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.16.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml

💤 Files with no reviewable changes (3)

• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.16.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.14.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.15.yaml

---

Walkthrough

This PR updates OpenShift multiarch CI test configurations across four nightly versions. Power-based SNO test jobs are removed from 4.14 and 4.16, replaced with an e2e-agent-ibmz-sno job in 4.15, and introduced as new test entries in 4.22, consolidating test coverage toward the latest nightly build.

Changes

PowerVS SNO Job Consolidation

Layer / File(s)	Summary
Removing power SNO jobs from stable versions ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.14.yaml, ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.16.yaml	Deleted ocp-e2e-sno-power from 4.14 and both ocp-e2e-sno-power and ocp-e2e-agent-sno-power from 4.16, simplifying their test job lists.
Consolidating SNO jobs in 4.15 ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.15.yaml	Removed ocp-assisted-sno-power, ocp-e2e-sno-power, and ocp-e2e-agent-sno-power jobs, replacing them with a single e2e-agent-ibmz-sno scheduled test invoking the agent-ibmz-sno-e2e workflow.
Adding power SNO jobs to 4.22 ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml	Inserted ocp-e2e-sno-power and ocp-e2e-agent-sno-power test jobs targeting powervs-1 with version 4.22, each with cron schedules and UPI workflow configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

ok-to-test

Suggested reviewers

• phani2898
• prb112

🚥 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: updating IBM Power Single-Node-OpenShift scheduling by removing jobs from older versions (4.15, 4.16) and adding them to newer versions (4.22, 4.23).
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	This PR modifies only CI configuration YAML files. No Ginkgo test code is present or modified in this pull request.
Test Structure And Quality	✅ Passed	PR modifies only CI/CD YAML configuration files (scheduling updates for IBM power jobs); no Ginkgo test code present to review, making the check not applicable.
Microshift Test Compatibility	✅ Passed	PR modifies only CI configuration YAML files. No new Ginkgo e2e tests are added, so the MicroShift compatibility check does not apply.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR modifies CI scheduling YAML configuration, not Ginkgo e2e test implementations. The custom check applies only to new test code with Ginkgo definitions, which are absent here.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only CI Prow job configuration files that define test scheduling, not deployment manifests, operator code, or controllers. No Kubernetes scheduling constraints are introduced.
Ote Binary Stdout Contract	✅ Passed	PR only modifies CI configuration YAML files, not OTE binary source code. The stdout contract check is inapplicable as no binary implementations are changed.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only CI job scheduling YAML configuration files. No new Ginkgo test code is added, so the IPv6/connectivity check does not apply.
No-Weak-Crypto	✅ Passed	PR only modifies CI configuration YAML files for test scheduling (adding/removing SNO Power test jobs). No cryptographic code, weak algorithms, or custom crypto implementations present.
Container-Privileges	✅ Passed	The PR modifies CI operator config files defining test jobs, not container/K8s manifests. No privileged settings, hostPID/Network/IPC, SYS_ADMIN, or root configurations found.
No-Sensitive-Data-In-Logs	✅ Passed	CI config file changes contain only non-sensitive job parameters (version numbers, install types, cron schedules). No passwords, tokens, API keys, PII, or sensitive logging statements present.

_{✏️ 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 and usage tips.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@mpkredhat: 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-multiarch-main-nightly-4.22-ocp-e2e-sno-power	N/A	periodic	Periodic changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-agent-sno-power	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.

[openshift-ci]

@mpkredhat: 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.

[prb112]

/pj-rehearse ack

[openshift-merge-bot]

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

[prb112]

/lgtm

[prb112]

/hold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpkredhat, prb112

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:

• ci-operator/config/openshift/multiarch/OWNERS [prb112]
• ci-operator/jobs/openshift/multiarch/OWNERS [prb112]

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