[Debug] Statistical validation of GCP sizing scheme (see #82852) by sdodson · Pull Request #83005 · openshift/release

sdodson · 2026-08-05T22:56:45Z

Summary

Rehearsal-only validation PR (⚠️ DO NOT MERGE), identical diff to #82852.

Purpose: gather enough rehearsal runs on the 10 GCP jobs where a two-proportion power calculation (90% confidence, 80% power, historical 30-day Sippy pass rate as baseline) makes it statistically tractable (<30 new runs) to either prove or disprove a ≥50% reduction in failure rate under the new sizing scheme (e2-custom-8-16384 non-serial CP / e2-custom-6-16384 serial CP / e2-standard-4 workers).

Kept on a separate branch/PR from #82852 so the real production PR doesn't accumulate dozens of rehearsal-trigger comments.

⚠️ DO NOT MERGE — rehearsal-only experiment.

Summary by CodeRabbit

This rehearsal updates OpenShift CI GCP jobs across release and nightly configurations.

Serial GCP jobs use e2-custom-6-16384 control-plane nodes.
Default GCP sizing uses e2-custom-8-16384 control-plane nodes and e2-standard-4 compute nodes.
Custom DNS jobs use e2-standard-8 for compute and control-plane nodes.
The changes validate the proposed sizing scheme through rehearsal runs.

…planes, e2-standard-4 workers Final production GCP sizing scheme, based on two rehearsal campaigns (openshift#82754, openshift#82856): - Control planes: change the shared ipi-conf-gcp default from e2-custom-6-16384 (6 vCPU / 16GB) to e2-custom-8-16384 (8 vCPU / 16GB). The prior default carried a code comment noting it was a "temporary test to see if this helps the consistent high CPU alerts and random test failures" - confirmed via a 12-run rehearsal campaign across 3 alternative instance types (openshift#82754) and a 30-day production survey across ~20 GCP 5.0 jobs, both showing e2-custom-8-16384 matches or beats e2-standard-8 on etcd fsync/commit latency and CPU saturation at ~13% lower cost. vCPU count (not memory ratio or CPU host platform) was the dominant driver: n2-standard-4 (4 vCPU) performed worse than the 6 vCPU baseline, every 8-vCPU option performed better. - Serial control planes: pinned back down to e2-custom-6-16384 via an explicit CONTROL_PLANE_NODE_TYPE override on every serial GCP job (51 jobs across 33 config files, using workflows openshift-e2e-gcp-serial{,-runc,-cgroupsv1}, openshift-e2e-gcp-ovn-serial, openshift-e2e-gcp-sdn-serial, openshift-e2e-gcp-techpreview-serial). Serial jobs run a non-parallel test suite and already show lower control-plane CPU utilization than non-serial jobs, and a 3-round study (openshift#82856) found downsizing them further to e2-standard-4 (4 vCPU) causes a clear, reproducible etcd disk-latency regression (fsync p99 elevated 29-113% above baseline in every round with data, including one round with real etcd overload errors: "etcdserver: too many requests", leader elections). A handful of old (nightly-4.6-4.16) jobs have "serial" in their as: name but run the parallel workflow (openshift-e2e-gcp/openshift-e2e-gcp-sdn) - left alone, since serial-ness is determined by workflow, not job name. - Workers: change the shared COMPUTE_NODE_TYPE default from e2-custom-6-16384 to e2-standard-4 for all GCP jobs (serial and non-serial). The same openshift#82856 campaign found no disqualifying etcd/CPU regression at this size across 3 rounds. - e2e-gcp-custom-dns (nightly-4.21/4.22/5.0): replaces the only 3 pre-existing CONTROL_PLANE_NODE_TYPE/COMPUTE_NODE_TYPE overrides in the repo, e2-custom-8-32768, with e2-standard-8. Both are 8 vCPU/32GB, but GCP's custom machine type pricing carries a ~5% premium over the equivalent predefined shape when the ratio matches a predefined tier exactly (confirmed via the GCP Cloud Billing Catalog API: $616.37/mo vs $587.02/mo for 3 nodes). Strict cost win, no behavior change. A further step-down to n4-standard-4 was also evaluated (openshift#82929, openshift#82934) but is not currently viable: some installer versions reject n4-standard-4's required hyperdisk-balanced disk type outright, and instances (workers, and in one case a control-plane node) intermittently vanished mid-provisioning with "can't find created instance" - consistent with GCP-side capacity/stockout behavior on the n4 family in the tested zones rather than a config issue. Revisit in the future once GCP capacity/tooling matures. Scope: only the shared *-case (amd64) defaults in ipi-conf-gcp-commands.sh are touched; xlarge/large/compact SIZE_VARIANT branches and the arm64 path (t2a-standard-4, unvalidated by this work) are untouched. Pre-existing per-job overrides elsewhere in the repo (e.g. jobs pinned to larger sizes for their own reasons) are left alone. rh-pre-commit.version: 2.4.0 rh-pre-commit.check-secrets: ENABLED

sdodson · 2026-08-05T22:56:54Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-rt-upgrade periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-rt periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-1of2 periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2 periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-upgrade periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

coderabbitai · 2026-08-05T22:57:13Z

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: b9dc62d9-a893-48c7-8272-b1e50b8820e0

📥 Commits

Reviewing files that changed from the base of the PR and between ceaff8c and 8fd8b7f.

📒 Files selected for processing (34)

ci-operator/config/openshift/release/openshift-release-main__ci-4.10.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.11.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.12.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.13.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.14.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.15.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.16.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.17.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.18.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.19.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.20.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.21.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.22.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-4.23.yaml
ci-operator/config/openshift/release/openshift-release-main__ci-5.0.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.10.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.11.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.12.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.13.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.14.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.15.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.16.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.17.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.18.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.19.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.20.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.21.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.22.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.23.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.7.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.8.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-4.9.yaml
ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml
ci-operator/step-registry/ipi/conf/gcp/ipi-conf-gcp-commands.sh

Walkthrough

The change updates GCP machine type defaults and adds explicit control-plane machine type overrides to release and nightly serial test configurations across multiple OpenShift versions.

Changes

GCP machine type configuration

Layer / File(s)	Summary
GCP provisioning defaults `ci-operator/step-registry/ipi/conf/gcp/ipi-conf-gcp-commands.sh`	The default control-plane type changes to `e2-custom-8-16384`. The default compute type changes to `e2-standard-4`.
Release test overrides `ci-operator/config/openshift/release/openshift-release-main__ci-*.yaml`	GCP serial release tests set `CONTROL_PLANE_NODE_TYPE` to `e2-custom-6-16384`.
Nightly test overrides `ci-operator/config/openshift/release/openshift-release-main__nightly-*.yaml`	GCP serial nightly tests set `CONTROL_PLANE_NODE_TYPE` to `e2-custom-6-16384`. Custom DNS jobs use `e2-standard-8` for compute and control-plane nodes.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

openshift/release#82852: Modifies the same GCP sizing defaults and serial-job control-plane overrides.

Suggested labels: 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 describes the statistical validation of the GCP sizing scheme, which matches the pull request objectives and changes.
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	The commit changes only YAML job configuration and a GCP shell script; the diff contains zero Ginkgo declarations, dynamic title constructs, IP addresses, or generated-name terms.
Test Structure And Quality	✅ Passed	HEAD^..HEAD changes 33 YAML release configurations and one shell script; no Ginkgo test files or Ginkgo constructs were changed, so these criteria do not apply.
Microshift Test Compatibility	✅ Passed	The commit changes only 33 YAML files and one GCP shell script; the patch adds no Ginkgo tests or test declarations, so MicroShift compatibility checks do not apply.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The diff changes only 33 YAML files and one GCP shell script; it adds no Ginkgo tests or multi-node test logic.
Topology-Aware Scheduling Compatibility	✅ Passed	The patch changes CI GCP machine-type environment values and install-config defaults only; it adds no operator, controller, deployment, or topology scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only YAML configuration and one GCP setup shell script; no Go/OTE binary or suite setup code changed, so this stdout contract is not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes only CI machine-type environment settings and GCP provisioning defaults; it adds no Ginkgo tests, IPv4 literals, URL construction, or external connectivity logic.
No-Weak-Crypto	✅ Passed	The patch only changes GCP machine-type environment values and defaults; added lines contain no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparisons.
Container-Privileges	✅ Passed	The PR only changes GCP machine-type environment values and defaults; added lines contain no privileged, host namespace, SYS_ADMIN, securityContext, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The commit adds only GCP machine-type settings and comments; scans found no credentials, PII, hostnames, or logging constructs in added lines.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-ci · 2026-08-05T22:57:53Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sdodson

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/release/OWNERS~~ [sdodson]
ci-operator/step-registry/ipi/conf/gcp/OWNERS

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

openshift-merge-bot · 2026-08-05T23:01:24Z

[REHEARSALNOTIFIER]
@sdodson: 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-kubevirt-hyperconverged-cluster-operator-release-1.7-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.6-hco-e2e-image-index-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.6-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.9-hco-e2e-image-index-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.9-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.8-hco-e2e-image-index-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.8-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-main-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.14-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.14-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.16-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.16-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.17-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.17-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.15-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.15-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.11-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.11-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.12-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.12-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.18-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.18-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.10-hco-e2e-operator-sdk-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed
pull-ci-kubevirt-hyperconverged-cluster-operator-release-1.10-hco-e2e-kv-smoke-gcp	kubevirt/hyperconverged-cluster-operator	presubmit	Registry content changed

A total of 6218 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
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-merge-bot · 2026-08-05T23:01:26Z

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

sdodson · 2026-08-06T01:19:24Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-1of2

openshift-merge-bot · 2026-08-06T01:19:26Z

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

sdodson · 2026-08-06T03:18:58Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2 periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-upgrade periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-rt

openshift-merge-bot · 2026-08-06T03:19:01Z

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

sdodson · 2026-08-06T04:18:41Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-rt-upgrade periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

openshift-merge-bot · 2026-08-06T04:18:45Z

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

sdodson · 2026-08-06T05:18:23Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-1of2

openshift-merge-bot · 2026-08-06T05:18:26Z

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

sdodson · 2026-08-06T06:19:02Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-06T06:19:05Z

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

sdodson · 2026-08-06T07:18:50Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-rt

openshift-merge-bot · 2026-08-06T07:19:57Z

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

sdodson · 2026-08-06T08:18:29Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2 periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-upgrade

openshift-merge-bot · 2026-08-06T08:18:32Z

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

sdodson · 2026-08-06T09:18:30Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-1of2 periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

openshift-merge-bot · 2026-08-06T09:18:33Z

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

sdodson · 2026-08-06T10:18:25Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-06T10:18:28Z

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

sdodson · 2026-08-06T11:21:32Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-rt periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview

openshift-merge-bot · 2026-08-06T11:21:35Z

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

sdodson · 2026-08-06T12:18:19Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-06T12:18:21Z

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

openshift-merge-bot · 2026-08-11T07:16:36Z

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

sdodson · 2026-08-11T09:16:23Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

openshift-merge-bot · 2026-08-11T09:16:27Z

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

sdodson · 2026-08-11T11:16:51Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

openshift-merge-bot · 2026-08-11T11:16:53Z

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

sdodson · 2026-08-11T12:16:26Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2

openshift-merge-bot · 2026-08-11T12:16:33Z

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

sdodson · 2026-08-11T13:16:32Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T13:21:37Z

@sdodson: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

sdodson · 2026-08-11T14:16:28Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T14:21:30Z

@sdodson: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

sdodson · 2026-08-11T15:16:27Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T15:21:30Z

@sdodson: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

sdodson · 2026-08-11T16:16:34Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

sdodson · 2026-08-11T16:16:35Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T16:21:36Z

@sdodson: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

openshift-merge-bot · 2026-08-11T16:21:37Z

@sdodson: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

sdodson · 2026-08-11T16:48:17Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T16:48:21Z

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

sdodson · 2026-08-11T17:16:43Z

/pj-rehearse periodic-ci-openshift-release-main-nightly-5.0-e2e-gcp-ovn-serial

sdodson · 2026-08-11T17:16:44Z

/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2

openshift-merge-bot · 2026-08-11T17:16:45Z

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

openshift-merge-bot · 2026-08-11T17:21:42Z

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

sdodson · 2026-08-11T22:16:32Z

/pj-rehearse periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-rt-upgrade

openshift-merge-bot · 2026-08-11T22:16:35Z

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

openshift-ci · 2026-08-12T03:32:14Z

@sdodson: 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/periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-upgrade	`8fd8b7f`	link	unknown	`/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-upgrade`
ci/rehearse/periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2	`8fd8b7f`	link	unknown	`/pj-rehearse periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview-serial-2of2`

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.

sdodson · 2026-08-12T17:43:50Z

/close

openshift-ci · 2026-08-12T17:44:07Z

@sdodson: Closed this PR.

Details

In response to this:

/close

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.

openshift-ci Bot requested review from smg247 and xueqzhan August 5, 2026 22:58

sdodson mentioned this pull request Aug 12, 2026

gcp: change default control-plane instance size from custom-6-16384 to custom-8-16384 #82852

Merged

2 of 4 tasks

openshift-ci Bot closed this Aug 12, 2026

Conversation

sdodson commented Aug 5, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Summary by CodeRabbit

Uh oh!

sdodson commented Aug 5, 2026

Uh oh!

coderabbitai Bot commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

openshift-ci Bot commented Aug 5, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 5, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 5, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

sdodson commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 6, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 11, 2026

Uh oh!

sdodson commented Aug 11, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 11, 2026

Uh oh!

sdodson commented Aug 11, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 11, 2026

Uh oh!

sdodson commented Aug 11, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 11, 2026

Uh oh!

sdodson commented Aug 11, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 11, 2026

sdodson commented Aug 5, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 5, 2026 •

edited

Loading