NO-ISSUE: bump master config to 5.0

[andfasano]

Otherwise main dev-scripts jobs will keep using a 4.22 release payload (see for example https://storage.googleapis.com/test-platform-results/pr-logs/pull/openshift-metal3_dev-scripts/1904/pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-compact-ipv4-iso-no-registry/2062794981382295552/build-log.txt)

Summary by CodeRabbit

This PR updates the CI configuration for the OpenShift Metal3 dev-scripts component to target OpenShift 5.0 instead of 4.22. Specifically, the changes update the container image and release payload versions used by CI jobs for this component:

• The build root container image is bumped from the 4.22-targeting variant (rhel-9-release-golang-1.24-openshift-4.22) to the 5.0-targeting variant (rhel-9-release-golang-1.26-openshift-5.0)
• The CI/CD integration releases are updated to reference version "5.0" for both the initial and latest release configurations

This ensures that dev-scripts CI jobs running against the master branch will use 5.0 release payloads instead of continuing to use the older 4.22 payloads.

[openshift-ci-robot]

@andfasano: This pull request explicitly references no jira issue.

Details

In response to this:

Otherwise main dev-scripts jobs will keep using a 4.22 release payload (see for example https://storage.googleapis.com/test-platform-results/pr-logs/pull/openshift-metal3_dev-scripts/1904/pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-compact-ipv4-iso-no-registry/2062794981382295552/build-log.txt)

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: 6c7eed3a-36b8-4320-8f3c-a0052d56b0c8

📥 Commits

Reviewing files that changed from the base of the PR and between 5ce5ea0 and d6f4f91.

📒 Files selected for processing (1)

• ci-operator/config/openshift-metal3/dev-scripts/openshift-metal3-dev-scripts-master.yaml

---

Walkthrough

Single-file configuration update to OpenShift Metal3 dev-scripts CI: the build_root image stream tag is bumped to use Golang 1.26 and OpenShift 5.0, and release integration labels are updated from version 4.22 to 5.0.

Changes

CI Configuration Version Upgrade

Layer / File(s)	Summary
Version 4.22 to 5.0 and Golang 1.24 to 1.26 upgrade ci-operator/config/openshift-metal3/dev-scripts/openshift-metal3-dev-scripts-master.yaml	Build root image stream tag and release integration version labels are coordinated to OpenShift 5.0 with Golang 1.26 runtime.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/release#77882: Both PRs directly update the build_root.image_stream_tag.tag YAML configuration to point to a different OpenShift/Golang release image tag (main: 4.22→5.0; retrieved: 4.22→4.23).
• openshift/release#77698: Both PRs update CI configuration to target OCP release 5.0 instead of 4.22 by changing versioned release/image inputs and --current-release/release labels.
• openshift/release#80114: Both PRs update the image-builder build_root.image_stream_tag.tag to the same new rhel-9-…-golang-1.26-openshift-5.0 version (with differing exact previous tags/extra metadata changes).

Suggested labels

lgtm, approved, rehearsals-ack

🚥 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: bumping the master configuration to version 5.0, which directly matches the changeset that updates version references from 4.22 to 5.0.
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 modifies only a YAML CI configuration file with static test workflow names (e.g., "e2e-metal-ipi-bm"). No Ginkgo tests or dynamic test names present.
Test Structure And Quality	✅ Passed	The PR modifies CI configuration YAML files (bumping versions 4.22→5.0), not Ginkgo test code. The check for Ginkgo test structure and quality is not applicable to configuration file changes.
Microshift Test Compatibility	✅ Passed	This PR only modifies CI/CD configuration (YAML file) and does not add any new Ginkgo e2e tests. The custom check for MicroShift test compatibility is not applicable when no new tests are introduced.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests (It/Describe/Context/When) are added in this PR - only a YAML CI configuration file is modified to bump versions from 4.22 to 5.0.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR only modifies a CI-operator configuration file with version bumps (4.22→5.0), not deployment manifests, operator code, or controllers. No scheduling constraints are introduced.
Ote Binary Stdout Contract	✅ Passed	PR modifies only CI configuration YAML files without adding any source code or stdout operations. The OTE Binary Stdout Contract check applies to executable code, not infrastructure configuration.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies CI configuration file (no Ginkgo e2e tests added). The check applies only to new e2e tests, so it's not applicable here.
No-Weak-Crypto	✅ Passed	PR is a CI configuration file update with version bumps (1.24→1.26, 4.22→5.0); contains no cryptographic code, weak algorithms, or secret comparisons.
Container-Privileges	✅ Passed	The modified CI-Operator config file contains no container privilege escalation settings (privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation).
No-Sensitive-Data-In-Logs	✅ Passed	PR contains only configuration file version updates (4.22→5.0, golang 1.24→1.26) with no logging statements or sensitive data exposure.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[andfasano]

/pj-rehearse

[openshift-merge-bot]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@andfasano: 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-metal3-dev-scripts-master-e2e-agent-4control-ipv4	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-5control-ipv4	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-bad-dns	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-compact-ipv4	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-compact-ipv4-iso-no-registry	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-ha-dualstack	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-agent-sno-ipv6	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-bm	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-bm-bond	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-ovn-dualstack	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-ovn-dualstack-v6	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-ovn-ipv6	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-serial-ipv4-1of2	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-serial-ipv4-2of2	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-serial-ovn-ipv6	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-upgrade	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-upgrade-ovn-ipv6	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-virtualmedia	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ovn-arbiter	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
pull-ci-openshift-metal3-dev-scripts-master-images	openshift-metal3/dev-scripts	presubmit	Ci-operator config changed
periodic-ci-openshift-metal3-dev-scripts-master-packetcheck-ipi-packet-check	N/A	periodic	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.

[andfasano]

/pj-rehearse pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ipi-virtualmedia pull-ci-openshift-metal3-dev-scripts-master-e2e-metal-ovn-arbiter

[openshift-merge-bot]

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

[andfasano]

cc @elfosardo

[bfournie]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, bfournie

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-metal3/dev-scripts/OWNERS [andfasano,bfournie]

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

[pawanpinjarkar]

/pj-rehearse ack

[openshift-merge-bot]

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

[openshift-ci]

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