OCPEDGE-3045: Add 5.0 and remove 4.17 release

[kasturinarra]

• Removing 4.17 as it reached EOL and no more updates for the release.
• Added 5.0 as i do not see this release being reported in the lvms ci doctor

Summary by CodeRabbit

• Updates LVM CI reporting to include OpenShift release 5.0.
• Removes OpenShift release 4.17 because it reached end of life.

[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: 2477069c-31ca-4608-af60-03b46eeb3923

📥 Commits

Reviewing files that changed from the base of the PR and between 1bd7187 and 6578636.

📒 Files selected for processing (1)

• ci-operator/step-registry/openshift/edge-tooling/lvms-ci/doctor/openshift-edge-tooling-lvms-ci-doctor-ref.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The LVMS doctor step configuration replaces release version 4.17 with 5.0 in its default RELEASE_VERSIONS list.

Changes

LVMS doctor release update

Layer / File(s)	Summary
Update configured release versions ci-operator/step-registry/openshift/edge-tooling/lvms-ci/doctor/openshift-edge-tooling-lvms-ci-doctor-ref.yaml	The RELEASE_VERSIONS default now includes 5.0 instead of 4.17.

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

Merge Risk: ⚪ Minimal · up to 65786

The LVMS doctor defaults now target 5.0 rather than the end-of-life 4.17 release. The change is ready to merge with no current actionable risk identified.

🚥 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. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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	PASS: The pull request changes only the static RELEASE_VERSIONS value in a YAML step reference. The diff adds 5.0 and removes 4.17; it adds no Ginkgo test titles or dynamic values in It(), `De…
Test Structure And Quality	✅ Passed	PASS — The pull request changes only the RELEASE_VERSIONS value in a YAML step definition. The diff contains no Ginkgo test code, It blocks, cluster setup, waits, or assertions. Therefore, the lis…
Microshift Test Compatibility	✅ Passed	PASS: The pull request changes only the RELEASE_VERSIONS value in a YAML step definition. The diff adds 5.0 and removes 4.17; it adds no Ginkgo tests and references no MicroShift APIs, namespace…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The pull request changes only the RELEASE_VERSIONS value in one YAML step-registry file. The diff adds 5.0 and removes 4.17; it adds no Ginkgo tests or test code. Therefore, the SNO compat…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS — The pull request changes only the RELEASE_VERSIONS environment default in a CI step reference: it adds 5.0 and removes 4.17. The value is passed to the LVMS doctor reporting script. The p…
Ote Binary Stdout Contract	✅ Passed	PASS: The pull request changes only the YAML value of RELEASE_VERSIONS, replacing 4.17 with 5.0. It does not change an OTE binary, main() or suite setup, or any stdout handling. The referenced…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS — The pull request changes only the RELEASE_VERSIONS value in one YAML file. It adds 5.0 and removes 4.17. The diff adds no Ginkgo e2e tests and introduces no IPv4 assumption or new externa…
No-Weak-Crypto	✅ Passed	PASS. The pull request changes only the RELEASE_VERSIONS YAML value: it adds 5.0 and removes 4.17. The diff introduces no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom cryptography, or secret…
Container-Privileges	✅ Passed	The pull request changes only the RELEASE_VERSIONS environment default in openshift-edge-tooling-lvms-ci-doctor-ref.yaml: it adds 5.0 and removes 4.17. The changed file and its diff contain no…
No-Sensitive-Data-In-Logs	✅ Passed	The pull request changes only the RELEASE_VERSIONS value from 4.17 to 5.0. These are release identifiers, not passwords, tokens, API keys, PII, hostnames, or customer data. The value is passed t…
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the issue and accurately summarizes the main change: add release 5.0 and remove release 4.17.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@kasturinarra: 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-eng-edge-tooling-main-lvms-ci-doctor	N/A	periodic	Registry content 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.

[kasturinarra]

/pj-rehearse periodic-ci-openshift-eng-edge-tooling-main-lvms-ci-doctor

[openshift-merge-bot]

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

[openshift-ci]

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

[openshift-ci-robot]

@kasturinarra: This pull request references OCPEDGE-3045 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.1.0" version, but no target version was set.

Details

In response to this:

• Removing 4.17 as it reached EOL and no more updates for the release.
• Added 5.0 as i do not see this release being reported in the lvms ci doctor

Summary by CodeRabbit

• Updates LVM CI reporting to include OpenShift release 5.0.
• Removes OpenShift release 4.17 because it reached end of life.

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.

[kasturinarra]

/pj-rehearse ack

[openshift-merge-bot]

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

[jeff-roche]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jeff-roche, kasturinarra

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/step-registry/openshift/edge-tooling/lvms-ci/doctor/OWNERS [jeff-roche,kasturinarra]

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