RHOBS-1582: rhobs/obs-mcp: run e2e on OCP 5.0 nightly

[slashpai]

#80078 updated only go image to 1.26, this updates cluster version also

Summary by CodeRabbit

This PR updates the OBS-MCP (Observability Multi-Cluster Platform) CI configuration to run end-to-end tests against OpenShift Container Platform 5.0 nightly builds instead of 4.22.

What changed:
The releases.latest.candidate.version field in ci-operator/config/rhobs/obs-mcp/rhobs-obs-mcp-main.yaml was updated from "4.22" to "5.0". This configuration controls which OCP release version the nightly CI test jobs provision for testing purposes.

Impact:

• The weekly e2e-obs-mcp test job (runs every Monday at 6 AM) will now deploy and test against OCP 5.0 nightly clusters instead of 4.22
• This change complements PR #80078, which previously updated the Go toolchain to version 1.26 for OpenShift 5.0 (the build_root already references rhel-9-release-golang-1.26-openshift-5.0)
• Ensures the obs-mcp component's CI testing stays aligned with the latest OCP development branch

Note: The PR is referenced against JIRA issue RHOBS-1582, though the CI system flagged that the issue lacks the proper target version metadata.

[openshift-ci-robot]

@slashpai: This pull request references RHOBS-1582 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

#80078 updated only go image to 1.26, this updates cluster version also

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]

Walkthrough

This PR updates the CI operator configuration for RHOBS OBS MCP by bumping the release candidate version from 4.22 to 5.0, reflecting the next major release cycle.

Changes

Release Candidate Version Update

Layer / File(s)	Summary
Release candidate version bump ci-operator/config/rhobs/obs-mcp/rhobs-obs-mcp-main.yaml	The releases.latest.candidate.version is updated from "4.22" to "5.0" to reflect the next major release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/release#80078: Both PRs modify the same YAML file ci-operator/config/rhobs/obs-mcp/rhobs-obs-mcp-main.yaml to bump OCP-related versions (this PR updates releases.latest.candidate.version to 5.0, while the retrieved PR updates the build image stream tag to OCP 5.0 / Golang 1.26).

Suggested reviewers

• iNecas
• tremes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the specific change: updating the cluster version to run e2e tests on OCP 5.0 nightly, which aligns with the YAML config update from version 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	This PR does not modify any Ginkgo test files or test definitions. It only updates YAML CI configuration and shell scripts, making the test name stability check inapplicable.
Test Structure And Quality	✅ Passed	PR contains only YAML configuration file changes (updating OCP version from 4.22 to 5.0), with no Ginkgo test code to review. Check is not applicable.
Microshift Test Compatibility	✅ Passed	PR adds CI configuration for running tests on OCP 5.0 but does not add any new Ginkgo e2e test code. Custom check only applies when new tests are added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR does not add new Ginkgo e2e tests; it only updates a CI configuration value (OCP version from 4.22 to 5.0). The check is not applicable to configuration-only changes.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates a CI configuration file's OCP version (4.22→5.0), not deployment manifests, operator code, or controllers. Topology-aware scheduling check does not apply.
Ote Binary Stdout Contract	✅ Passed	PR contains only YAML configuration change (cluster version 4.22→5.0); no code modifications that could affect OTE binary stdout contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only modifies CI configuration YAML (updates cluster version to 5.0), not Ginkgo e2e tests. Check applies only to new e2e tests.
No-Weak-Crypto	✅ Passed	The PR modifies only a YAML config file, updating cluster version from 4.22 to 5.0. No cryptographic code, weak algorithms, custom crypto, or secret comparisons are present.
Container-Privileges	✅ Passed	The pull request modifies a CI operator configuration file with only a version number change. No Kubernetes container manifests or privileged container settings are present in the changed file.
No-Sensitive-Data-In-Logs	✅ Passed	PR only updates a version number (4.22 to 5.0) in a CI configuration file. No logging code, secrets, passwords, tokens, API keys, PII, or sensitive data present.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: slashpai

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/rhobs/obs-mcp/OWNERS [slashpai]
• ci-operator/jobs/rhobs/obs-mcp/OWNERS [slashpai]

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

[slashpai]

/pj-rehearse

[openshift-merge-bot]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@slashpai: 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-rhobs-obs-mcp-main-e2e-obs-mcp-gcp	rhobs/obs-mcp	presubmit	Ci-operator config changed
pull-ci-rhobs-obs-mcp-main-images	rhobs/obs-mcp	presubmit	Ci-operator config changed
periodic-ci-rhobs-obs-mcp-main-e2e-obs-mcp	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.

[openshift-ci]

@slashpai: The following tests 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/rhobs/obs-mcp/main/e2e-obs-mcp-gcp	2cd816d	link	unknown	/pj-rehearse pull-ci-rhobs-obs-mcp-main-e2e-obs-mcp-gcp
ci/rehearse/periodic-ci-rhobs-obs-mcp-main-e2e-obs-mcp	2cd816d	link	unknown	/pj-rehearse periodic-ci-rhobs-obs-mcp-main-e2e-obs-mcp

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.