OCPBUGS-85346: Revert 4.22 and 4.23 from C4A to T2A instances to avoid hyperdisk costs

[barbacbd]

This reverts 4.22 and 4.23 multi-arch GCP jobs from C4A (Axion) instances back to T2A (Tau) instances to avoid the cost increase associated with hyperdisk-balanced storage.

Root Cause of StatefulSet Failures

C4A instances only support Hyperdisk storage types and do NOT support Persistent Disk types (pd-standard, pd-balanced, pd-ssd). When StatefulSet tests create PVCs using the cluster's default StorageClass (standard-csi with pd-standard), volume attach fails on C4A nodes:

googleapi: Error 400: pd-standard disk type cannot be used by
c4a-standard-2 machine type., badRequest

The Fix: Revert to T2A

Instead of adding hyperdisk-balanced StorageClass (which increases costs), revert 4.22 and 4.23 to T2A instances which support pd-standard.

Cost Considerations

• pd-standard: ~$0.04/GB/month (T2A compatible)
• hyperdisk-balanced: ~$0.10-0.12/GB/month + IOPS charges (C4A required)

For CI jobs with many PVCs (monitoring, logging, registry, StatefulSets), using hyperdisk-balanced across all test runs would significantly increase costs. T2A with pd-standard is more cost-effective.

Quota Mitigation

While reverting to T2A means 4.21, 4.22, and 4.23 will compete for the same T2A quota, PR #77809 included other mitigations that remain in place:

1. Zone randomization - Distributes instances across zones
2. Interval scheduling (168h) - Prevents simultaneous execution
3. Smaller instances - Uses t2a-standard-2 (not standard-4)
4. Balanced worker layout - 2+2 workers instead of 3+2

These mitigations should reduce quota pressure even with multiple releases using T2A.

Changes Made

4.22 nightly config (6 jobs):

• ocp-e2e-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-x-to-a-x: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-a-a-to-x-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-ax: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-x-ax: c4a-standard-2 → t2a-standard-2

4.23 nightly config (5 jobs):

• ocp-e2e-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-x-to-a-x: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-a-a-to-x-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• Heterogeneous jobs: c4a-standard-2 → t2a-standard-2

4.22 upgrade configs (2 files):

• nightly-4.22-upgrade-from-nightly-4.21: c4a-standard-4 → t2a-standard-4
• nightly-4.22-upgrade-from-stable-4.21: c4a-standard-4 → t2a-standard-4

4.23 upgrade configs (2 files):

• nightly-4.23-upgrade-from-nightly-4.22: c4a-standard-2 → t2a-standard-2
• nightly-4.23-upgrade-from-stable-4.22: c4a-standard-2 → t2a-standard-2

Removed ADDITIONAL_WORKER_DISK_TYPE: hyperdisk-balanced from all heterogeneous jobs (no longer needed as T2A supports pd-standard).

Release Distribution After This Change

• 4.21: T2A standard-2
• 4.22: T2A standard-2 (reverted from C4A)
• 4.23: T2A standard-2 (reverted from C4A)
• 5.0: T2A standard-4

References

• JIRA: https://redhat.atlassian.net/browse/OCPBUGS-85346
• Failed job: periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-x-ax
• Original PR OCPBUGS-82060: Distribute GCP ARM64 instance types across releases to reduce quota exhaustion #77809: OCPBUGS-82060: Distribute GCP ARM64 instance types across releases to reduce quota exhaustion #77809
• GCP C4A disk requirements: https://cloud.google.com/blog/products/compute/first-google-axion-processor-c4a-now-ga-with-titanium-ssd

OpenShift CI Configuration: Revert GCP Multi-Arch Jobs from C4A to T2A Instances

This PR reverts GCP multi-architecture CI job configurations for OpenShift 4.22 and 4.23 from C4A (Axion) instances back to T2A (Tau) instances to reduce storage costs.

Problem Being Addressed

C4A instances require hyperdisk-balanced storage (approximately $0.10–0.12/GB/month plus IOPS costs), while T2A instances support cheaper pd-standard storage (approximately $0.04/GB/month). The C4A instances were incompatible with standard persistent volume storage, causing PVC attachment failures in StatefulSet tests. This change restores compatibility with pd-standard storage while avoiding the higher cost of hyperdisk infrastructure.

Configuration Changes

Five CI configuration files in ci-operator/config/openshift/multiarch/ were updated:

1. openshift-multiarch-main__nightly-4.22.yaml: Updated six jobs from c4a-standard-2 to t2a-standard-2 for compute and control plane nodes; removed ADDITIONAL_WORKER_DISK_TYPE: hyperdisk-balanced from heterogeneous worker configuration.

2. openshift-multiarch-main__nightly-4.22-upgrade-from-nightly-4.21.yaml: Changed additional worker VM type from c4a-standard-4 to t2a-standard-4.

3. openshift-multiarch-main__nightly-4.22-upgrade-from-stable-4.21.yaml: Changed additional worker VM type from c4a-standard-4 to t2a-standard-4 and removed ADDITIONAL_WORKER_DISK_TYPE.

4. openshift-multiarch-main__nightly-4.23.yaml: Updated five jobs from c4a-standard-2 to t2a-standard-2; removed ADDITIONAL_WORKER_DISK_TYPE: hyperdisk-balanced from heterogeneous configurations.

5. openshift-multiarch-main__nightly-4.23-upgrade-from-nightly-4.22.yaml and openshift-multiarch-main__nightly-4.23-upgrade-from-stable-4.22.yaml: Changed additional worker VM types from c4a-standard-2 to t2a-standard-2 and removed hyperdisk-balanced disk type setting.

Affected Jobs

• 4.22 nightly: six heterogeneous and migration jobs
• 4.23 nightly: five heterogeneous and migration jobs
• Upgrade jobs (both nightly-to-nightly and stable-to-nightly paths for 4.22 and 4.23)

Resource Allocation Impact

This change consolidates versions 4.21, 4.22, and 4.23 to use T2A standard-2 instances, while 5.0 continues with T2A standard-4. Quota management relies on existing mitigations including zone randomization, 168-hour scheduling intervals, and balanced worker distribution (2+2).

[openshift-ci-robot]

@barbacbd: This pull request references Jira Issue OCPBUGS-85346, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This reverts 4.22 and 4.23 multi-arch GCP jobs from C4A (Axion) instances back to T2A (Tau) instances to avoid the cost increase associated with hyperdisk-balanced storage.

Root Cause of StatefulSet Failures

C4A instances only support Hyperdisk storage types and do NOT support Persistent Disk types (pd-standard, pd-balanced, pd-ssd). When StatefulSet tests create PVCs using the cluster's default StorageClass (standard-csi with pd-standard), volume attach fails on C4A nodes:

googleapi: Error 400: pd-standard disk type cannot be used by
c4a-standard-2 machine type., badRequest

The Fix: Revert to T2A

Instead of adding hyperdisk-balanced StorageClass (which increases costs), revert 4.22 and 4.23 to T2A instances which support pd-standard.

Cost Considerations

• pd-standard: ~$0.04/GB/month (T2A compatible)
• hyperdisk-balanced: ~$0.10-0.12/GB/month + IOPS charges (C4A required)

For CI jobs with many PVCs (monitoring, logging, registry, StatefulSets), using hyperdisk-balanced across all test runs would significantly increase costs. T2A with pd-standard is more cost-effective.

Quota Mitigation

While reverting to T2A means 4.21, 4.22, and 4.23 will compete for the same T2A quota, PR #77809 included other mitigations that remain in place:

1. Zone randomization - Distributes instances across zones
2. Interval scheduling (168h) - Prevents simultaneous execution
3. Smaller instances - Uses t2a-standard-2 (not standard-4)
4. Balanced worker layout - 2+2 workers instead of 3+2

These mitigations should reduce quota pressure even with multiple releases using T2A.

Changes Made

4.22 nightly config (6 jobs):

• ocp-e2e-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-x-to-a-x: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-a-a-to-x-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-ax: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-x-ax: c4a-standard-2 → t2a-standard-2

4.23 nightly config (5 jobs):

• ocp-e2e-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-x-x-to-a-x: c4a-standard-2 → t2a-standard-2
• ocp-e2e-gcp-ovn-multi-a-a-to-x-a: c4a-standard-2 → t2a-standard-2
• ocp-e2e-upgrade-gcp-ovn-multi-a-a: c4a-standard-2 → t2a-standard-2
• Heterogeneous jobs: c4a-standard-2 → t2a-standard-2

4.22 upgrade configs (2 files):

• nightly-4.22-upgrade-from-nightly-4.21: c4a-standard-4 → t2a-standard-4
• nightly-4.22-upgrade-from-stable-4.21: c4a-standard-4 → t2a-standard-4

4.23 upgrade configs (2 files):

• nightly-4.23-upgrade-from-nightly-4.22: c4a-standard-2 → t2a-standard-2
• nightly-4.23-upgrade-from-stable-4.22: c4a-standard-2 → t2a-standard-2

Removed ADDITIONAL_WORKER_DISK_TYPE: hyperdisk-balanced from all heterogeneous jobs (no longer needed as T2A supports pd-standard).

Release Distribution After This Change

• 4.21: T2A standard-2
• 4.22: T2A standard-2 (reverted from C4A)
• 4.23: T2A standard-2 (reverted from C4A)
• 5.0: T2A standard-4

References

• JIRA: https://redhat.atlassian.net/browse/OCPBUGS-85346
• Failed job: periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-x-ax
• Original PR OCPBUGS-82060: Distribute GCP ARM64 instance types across releases to reduce quota exhaustion #77809: OCPBUGS-82060: Distribute GCP ARM64 instance types across releases to reduce quota exhaustion #77809
• GCP C4A disk requirements: https://cloud.google.com/blog/products/compute/first-google-axion-processor-c4a-now-ga-with-titanium-ssd

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: barbacbd
Once this PR has been reviewed and has the lgtm label, please assign prashanth684 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/multiarch/OWNERS

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

[coderabbitai]

Walkthrough

This PR updates GCP machine type configurations across six ci-operator multiarch release configurations (versions 4.22 and 4.23). The changes replace c4a-standard-* instances with t2a-standard-* for compute, control plane, and worker nodes, and remove ADDITIONAL_WORKER_DISK_TYPE settings where present.

Changes

GCP Machine Type Migration

Layer / File(s)	Summary
Nightly 4.22 Config ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml	Node and migration machine types updated from c4a-standard-2 to t2a-standard-2 across multiple test workflows. Worker disk type setting removed for multi-architecture heterogeneous jobs.
4.22 Upgrade Configs ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22-upgrade-*.yaml	Additional worker VM type changed from c4a-standard-4 to t2a-standard-4 in upgrade test steps. ADDITIONAL_WORKER_DISK_TYPE removed where configured.
Nightly 4.23 Config ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml	Node and migration machine types updated from c4a-standard-2 to t2a-standard-2 across multiple workflows. Worker disk type setting removed for heterogeneous test jobs.
4.23 Upgrade Configs ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23-upgrade-*.yaml	Additional worker VM type changed from c4a-standard-2 to t2a-standard-2 in upgrade test environments. Disk type configuration removed from test step settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: reverting GCP multi-arch CI jobs for OpenShift 4.22 and 4.23 from C4A to T2A instances to avoid hyperdisk costs. It is concise, directly related to the changeset, and provides meaningful context about what was changed and why.
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 custom check for stable Ginkgo test names is not applicable. This PR modifies only YAML CI configuration files (VM type changes), not Ginkgo test code or test definitions.
Test Structure And Quality	✅ Passed	This PR modifies only CI configuration YAML files, not Ginkgo test code. The check for Ginkgo test structure and quality is not applicable.
Microshift Test Compatibility	✅ Passed	PR contains only CI infrastructure configuration changes (VM type updates), not new Ginkgo e2e tests. Check applies only to new Ginkgo tests.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only CI config YAML files, not test code. No new Ginkgo tests added. Check targets new test code and is not applicable here.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies CI test configuration files, not deployment manifests or operator code. The custom check applies only to the latter, so it is not applicable here.
Ote Binary Stdout Contract	✅ Passed	PR modifies only YAML CI configuration. Check targets executable code (Go binaries). No code changes present.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR contains only CI YAML config changes to GCP machine types (c4a→t2a). No new Ginkgo tests added, so IPv6/disconnected network check is not applicable.

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

[coderabbitai]

🧹 Nitpick comments (1)

ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml (1)

749-760: Track T2A quota pressure after rollout.

Given these lane-wide shifts, it’s worth adding/confirming alerting on pending-job spikes and GCP quota exhaustion for T2A pools.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml`
around lines 749 - 760, This job config switches to T2A instances
(COMPUTE_NODE_TYPE and CONTROL_PLANE_NODE_TYPE set to t2a-standard-2 with
OCP_ARCH: arm64 and workflow: openshift-e2e-gcp-ovn), so add or reference
alerting for T2A quota and pending-job spikes: create/update Prometheus alert
rules tied to these identifiers (use labels/annotations derived from
COMPUTE_NODE_TYPE, CONTROL_PLANE_NODE_TYPE, OCP_ARCH, workflow and the job “as”
value) that fire on sustained increases in pending Kubernetes jobs or GCP
CPU/quota exhaustion for t2a-standard-2 (also include MIGRATION_CP_MACHINE_TYPE
/ MIGRATION_INFRA_MACHINE_TYPE where relevant); attach the alerts to the job via
metadata/annotations or include an alerts reference so on rollout we get
notified of pending-job spikes and T2A quota exhaustion.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml`:
- Around line 749-760: This job config switches to T2A instances
(COMPUTE_NODE_TYPE and CONTROL_PLANE_NODE_TYPE set to t2a-standard-2 with
OCP_ARCH: arm64 and workflow: openshift-e2e-gcp-ovn), so add or reference
alerting for T2A quota and pending-job spikes: create/update Prometheus alert
rules tied to these identifiers (use labels/annotations derived from
COMPUTE_NODE_TYPE, CONTROL_PLANE_NODE_TYPE, OCP_ARCH, workflow and the job “as”
value) that fire on sustained increases in pending Kubernetes jobs or GCP
CPU/quota exhaustion for t2a-standard-2 (also include MIGRATION_CP_MACHINE_TYPE
/ MIGRATION_INFRA_MACHINE_TYPE where relevant); attach the alerts to the job via
metadata/annotations or include an alerts reference so on rollout we get
notified of pending-job spikes and T2A quota exhaustion.

---

ℹ️ Review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: eb5f3be0-e742-4f7a-9125-38a7baff8ee7

📥 Commits

Reviewing files that changed from the base of the PR and between 5c055d8 and 2042841.

📒 Files selected for processing (6)

• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22-upgrade-from-nightly-4.21.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22-upgrade-from-stable-4.21.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.22.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23-upgrade-from-nightly-4.22.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23-upgrade-from-stable-4.22.yaml
• ci-operator/config/openshift/multiarch/openshift-multiarch-main__nightly-4.23.yaml

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@barbacbd: 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
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-a-a-to-x-a	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-upgrade-gcp-ovn-multi-a-a	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-upgrade-from-stable-4.22-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-x-x-to-a-x	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-upgrade-from-nightly-4.22-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-a-a	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-upgrade-from-nightly-4.21-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-x-x-to-a-x	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-upgrade-from-stable-4.21-ocp-e2e-upgrade-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-a-a-to-x-a	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-x-ax	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-a-a	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-upgrade-gcp-ovn-multi-a-a	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.

[gnufied]

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-a-a-to-x-a

[openshift-merge-bot]

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

[openshift-ci]

@barbacbd: 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/periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-a-a-to-x-a	2042841	link	unknown	/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-gcp-ovn-multi-a-a-to-x-a

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.

[gnufied]

/payload periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-gcp-ovn-multi-x-ax