stolostron/multicluster-global-hub: use go1.26-linux builder for release-2.15

[birsanv]

Summary

• Bump OpenShift CI build_root and base_images from go1.25-linux to go1.26-linux for stolostron-multicluster-global-hub-release-2.15

Why

Companion to GH 1.6 hub go.mod bump — Prow jobs using from: src need go1.26-linux after hub go.mod moves to 1.26.3.

Follows #81274 pattern.

Test plan

• ci/prow/checkconfig passes
• /pj-rehearse pull-ci-stolostron-multicluster-global-hub-release-2.15-sonarcloud after hub PR merges

Made with Cursor

Made with Cursor

[birsanv]

Update: go1.26-linux builder for release-2.15

• Bumped base_images and build_root to go1.26-linux for stolostron-multicluster-global-hub-release-2.15
• Companion to stolostron/multicluster-global-hub Remove systemd-devel test dependency #2604

[coderabbitai]

Warning

Review limit reached

@birsanv, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 34b4ac98-0f17-4550-8cb1-dd470a14fe3d

📥 Commits

Reviewing files that changed from the base of the PR and between 9699520 and 9d30592.

📒 Files selected for processing (1)

• ci-operator/config/stolostron/multicluster-global-hub/stolostron-multicluster-global-hub-release-2.15.yaml

✨ 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]
@birsanv: 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-stolostron-multicluster-global-hub-release-2.15-images	stolostron/multicluster-global-hub	presubmit	Ci-operator config changed
pull-ci-stolostron-multicluster-global-hub-release-2.15-sonarcloud	stolostron/multicluster-global-hub	presubmit	Ci-operator config changed
pull-ci-stolostron-multicluster-global-hub-release-2.15-test-e2e	stolostron/multicluster-global-hub	presubmit	Ci-operator config changed
pull-ci-stolostron-multicluster-global-hub-release-2.15-test-integration	stolostron/multicluster-global-hub	presubmit	Ci-operator config changed
pull-ci-stolostron-multicluster-global-hub-release-2.15-test-unit	stolostron/multicluster-global-hub	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.

[bjoydeep]

/lgtm /approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: birsanv, bjoydeep

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/stolostron/multicluster-global-hub/OWNERS [birsanv,bjoydeep]

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

[birsanv]

/pj-rehearse

[openshift-merge-bot]

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

[openshift-merge-bot]

@birsanv, pj-rehearse: unable prepare a candidate for rehearsal; rehearsals will not be run. This could be due to a branch that needs to be rebased. ERROR:

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

[birsanv]

/pj-rehearse

[openshift-merge-bot]

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

[birsanv]

/retest-required

[birsanv]

Update: rehearsal failure investigation

PR change: ci-operator-only go1.26-linux bump for release-2.15 — all openshift/release validation passes.

Passing rehearsals: images, test-unit, test-e2e

Failed rehearsals (not caused by builder bump):

Job	Cause
sonarcloud	Ran against hub 92b565c (pre-#2610): unpinned go install .../ginkgo (S8545) + floating run-gemini-cli@v0 (S7637). Fixed on release-2.15 by stolostron/multicluster-global-hub#2610 (merged). Re-run sonar rehearsal below.
test-integration	Flaky MigrationFromSyncer / should rollback initializing stage successfully — 10s timeout waiting for annotation cleanup (migration_from_syncer_test.go:407). Unrelated to builder.

Same unblock pattern as #81354 / #81355.

/pj-rehearse pull-ci-stolostron-multicluster-global-hub-release-2.15-sonarcloud
/pj-rehearse ack

[openshift-merge-bot]

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

[openshift-ci]

@birsanv: 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/stolostron/multicluster-global-hub/release-2.15/test-integration	9d30592	link	unknown	/pj-rehearse pull-ci-stolostron-multicluster-global-hub-release-2.15-test-integration

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.