nvidia-ci Test OCP 5 dev-preview

[josecastillolema]

Summary by CodeRabbit

Updates the rh-ecosystem-edge/nvidia-ci CI configuration for OpenShift 5 testing so the OCP 5.0-stable release jobs now track the 5-dev-preview prerelease stream instead of 4-stable. This affects both the arm64-latest and latest release entries, aligning NVIDIA CI with the newer dev-preview content for OpenShift 5.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josecastillolema

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/rh-ecosystem-edge/nvidia-ci/OWNERS [josecastillolema]

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: Enterprise

Run ID: 26d721a5-d5bd-4d8e-b3f0-d7dc838b6d52

📥 Commits

Reviewing files that changed from the base of the PR and between a3d3eee and 0a6af0f.

📒 Files selected for processing (1)

• ci-operator/config/rh-ecosystem-edge/nvidia-ci/rh-ecosystem-edge-nvidia-ci-main__5.0-stable.yaml

---

Walkthrough

This change updates a CI configuration YAML file, modifying the prerelease stream value from 4-stable to 5-dev-preview for both arm64-latest and latest release entries under the 5.0-stable configuration.

Changes

Prerelease Stream Update

Layer / File(s)	Summary
Update prerelease stream configuration ci-operator/config/rh-ecosystem-edge/nvidia-ci/rh-ecosystem-edge-nvidia-ci-main__5.0-stable.yaml	Changes prerelease.stream from 4-stable to 5-dev-preview for both arm64-latest and latest release entries, leaving other prerelease bounds/products unchanged.

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 matches the main change: updating nvidia-ci to test OCP 5 dev-preview.
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 updates release stream values in a YAML config; no Ginkgo test titles were added or changed.
Test Structure And Quality	✅ Passed	PR only changes CI/job YAML; no Go/Ginkgo test code or Ginkgo symbols were modified, so the Ginkgo quality check is not applicable.
Microshift Test Compatibility	✅ Passed	Only a ci-operator YAML prerelease stream changed; no new Ginkgo tests or test code were added, so MicroShift compatibility is not implicated.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only a ci-operator YAML was changed; no Ginkgo/e2e test code or SNO-sensitive test additions are present.
Topology-Aware Scheduling Compatibility	✅ Passed	Only the prerelease stream changed in a ci-operator YAML; no manifests, controllers, replicas, or scheduling constraints were introduced.
Ote Binary Stdout Contract	✅ Passed	PR only updates a ci-operator YAML prerelease stream; no binary or suite setup code changed, so the stdout contract isn’t implicated.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only a ci-operator release-stream YAML changed; no Ginkgo tests, IP handling, or external connectivity code was added, so the check is not applicable.
No-Weak-Crypto	✅ Passed	The PR only updates YAML release stream values; no weak-crypto algorithms, custom crypto, or secret comparisons are present.
Container-Privileges	✅ Passed	PASS: The only change updates release prerelease streams; the YAML contains no privileged, hostPID/Network/IPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The only change is a release stream swap; no new log lines, secrets, PII, tokens, or hostnames were added.

✨ 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]
@josecastillolema: 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-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-images	rh-ecosystem-edge/nvidia-ci	presubmit	Ci-operator config changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-25-10-x	rh-ecosystem-edge/nvidia-ci	presubmit	Ci-operator config changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-26-3-x	rh-ecosystem-edge/nvidia-ci	presubmit	Ci-operator config changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-arm64	rh-ecosystem-edge/nvidia-ci	presubmit	Ci-operator config changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-master	rh-ecosystem-edge/nvidia-ci	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.

[josecastillolema]

/pj-rehearse pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-arm64

[openshift-merge-bot]

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

[openshift-ci]

@josecastillolema: 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/rh-ecosystem-edge/nvidia-ci/main/5.0-stable-nvidia-gpu-operator-e2e-arm64	0a6af0f	link	unknown	/pj-rehearse pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-arm64

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.