rosa-backend-tests: update build root to Go 1.26 for Go 1.26.8 compatibility

[redhat-chai-bot]

Summary

Update the ci-operator build root image for openshift-online/rosa-backend-tests from Go 1.24 to Go 1.26.

Details

PR openshift-online/rosa-backend-tests#136 bumps go.mod from go 1.24.7 to go 1.26.8. The current build root image (rhel-9-release-golang-1.24-openshift-4.22) ships Go 1.24.11 with GOTOOLCHAIN=local baked into the binary, preventing the toolchain auto-download that go 1.26.8 requires.

This change updates the build root to rhel-9-release-golang-1.26-openshift-4.22, which provides a Go 1.26 toolchain compatible with the new go.mod requirement.

Change

-    tag: rhel-9-release-golang-1.24-openshift-4.22
+    tag: rhel-9-release-golang-1.26-openshift-4.22

---

AI-generated. Review for accuracy.

@andreadecorte requested via Chai Bot

[coderabbitai]

Warning

Review limit reached

Next included review available in 12 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: a84c0152-8048-42d6-907c-721b45cb4ab3

📥 Commits

Reviewing files that changed from the base of the PR and between 432718b and 73ff7c1.

📒 Files selected for processing (1)

• ci-operator/config/openshift-online/rosa-backend-tests/openshift-online-rosa-backend-tests-master.yaml

---

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

[openshift-merge-bot]

@redhat-chai-bot, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't checkout base SHA 380e6e8996e4b991845180400ed096083c8edd17: error checking out "380e6e8996e4b991845180400ed096083c8edd17": exit status 128 fatal: unable to read tree (380e6e8996e4b991845180400ed096083c8edd17)

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]

[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 bhushanthakur93 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-online/rosa-backend-tests/OWNERS

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

[openshift-ci]

@redhat-chai-bot: 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.