Bump Sippy e2e cluster_claim version from 4.18 to 4.22

[redhat-chai-bot]

Summary

The Sippy e2e presubmit job (pull-ci-openshift-sippy-main-e2e) is permafailing because the cluster_claim in the ci-operator config is pinned to version: "4.18", and that cluster pool is no longer servicing claims.

Error: failed to list cluster pools with list option map[architecture:amd64 cloud:aws owner:openshift-ci product:ocp version:4.18]

Changes

Bumps the cluster claim version from 4.18 to 4.22 in ci-operator/config/openshift/sippy/openshift-sippy-main.yaml.

The Sippy e2e test deploys Sippy against a running cluster and does not exercise OCP version-specific behavior, so the exact cluster version does not matter — it just needs a healthy, available pool.

make ci-operator-config and make jobs both pass cleanly with no additional generated diffs (the version is resolved at runtime by ci-operator).

---

AI-generated. Review for accuracy.

@neisw requested in Slack thread

Summary by CodeRabbit

• Updates the Sippy e2e presubmit job to request OpenShift 4.22 clusters instead of 4.18.
• Restores cluster provisioning because the 4.18 cluster pool no longer services claims.
• Keeps the Sippy e2e test independent of a specific OpenShift version.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign neisw 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/sippy/OWNERS

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

[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: 18cc6a78-dfa8-4d6e-80eb-67018fa67f4d

📥 Commits

Reviewing files that changed from the base of the PR and between d3c6320 and 86b6d67.

📒 Files selected for processing (1)

• ci-operator/config/openshift/sippy/openshift-sippy-main.yaml

---

Walkthrough

The e2e test cluster claim now targets OpenShift version 4.22 instead of 4.18.

Changes

OpenShift cluster target

Layer / File(s)	Summary
Update cluster claim version ci-operator/config/openshift/sippy/openshift-sippy-main.yaml	The e2e cluster claim version changes from 4.18 to 4.22.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 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 and concisely describes the cluster_claim version change from 4.18 to 4.22.
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 PR changes only the YAML cluster_claim version from 4.18 to 4.22; it adds or modifies no Ginkgo test titles.
Test Structure And Quality	✅ Passed	PASS: The PR changes only a YAML cluster_claim version; no Ginkgo It blocks or test setup, cleanup, waits, or assertions are modified.
Microshift Test Compatibility	✅ Passed	The commit changes only a YAML cluster_claim version from 4.18 to 4.22; it adds no Ginkgo e2e tests requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit only changes the YAML cluster_claim version from 4.18 to 4.22; it adds no Ginkgo e2e tests requiring SNO compatibility review.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit changes only the ci-operator cluster_claim version from 4.18 to 4.22; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only the cluster_claim version in a YAML config; it adds no OTE binary, Go source, suite setup, or stdout/logging code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The patch changes only the cluster_claim version in one YAML file; it adds no Ginkgo tests or IPv4/external-connectivity code.
No-Weak-Crypto	✅ Passed	The only change is cluster_claim version 4.18 to 4.22; the diff adds no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons.
Container-Privileges	✅ Passed	The commit changes only cluster_claim.version from 4.18 to 4.22; it adds no privileged, host namespace, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes only cluster_claim.version from 4.18 to 4.22; the diff adds no logging statements or sensitive values.

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

[REHEARSALNOTIFIER]
@redhat-chai-bot: 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
pull-ci-openshift-sippy-main-e2e	openshift/sippy	presubmit	Ci-operator config 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.

[redhat-chai-bot]

/pj-rehearse pull-ci-openshift-sippy-main-e2e

---

AI-generated. Review for accuracy.

[openshift-merge-bot]

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

[openshift-ci]

@redhat-chai-bot: 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/rehearse/openshift/sippy/main/e2e	86b6d67	link	unknown	/pj-rehearse pull-ci-openshift-sippy-main-e2e

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.