CNTRLPLANE-2207: Upgrade to CAPI 1.11 by clebs · Pull Request #7590 · openshift/hypershift

clebs · 2026-01-27T09:56:24Z

What this PR does / why we need it:

Bumps hypershift to use CAPI v1.11 including the following tasks:

Update CAPI and all providers to a v1.11 compatible version in go.mod.
Removes @csrwng's fork containing a temporary fix.
Update controller-gen goal in Makefile.
Update install assets: CAPI CRDs.
Patch CAPI CRDs to use v1beta1 as storage version.
Adds conversion webhooks for v1beta1 <-> v1beta2.
Removes the temporary CAPI image overrides (OCPBUGS-74247: CAPI image overrides aware of registry config #7575).
Check in updated vendored dependencies.

Which issue(s) this PR fixes:

Fixes CNTRLPLANE-2207

Special notes for your reviewer:

Checklist:

Subject and description added to both, commit and PR.
Relevant issues have been referenced.
This change includes docs.
This change includes unit tests.

Summary by CodeRabbit

Release Notes

Chores
- Updated Go module dependencies to newer versions for improved stability and security.
- Adjusted build configuration for CRD generation to optimize the build process.
- Updated linter configuration to address deprecated package deprecations.

coderabbitai · 2026-01-27T09:56:33Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

📝 Walkthrough

Walkthrough

The pull request makes three configuration and dependency-related updates. It adds a new staticcheck exclusion rule in .golangci.yml for a deprecated Kubernetes Cluster API package path. The Makefile is updated to narrow the controller-gen CRD generation input paths from broader vendor scans to more specific paths under api/core and api/ipam. The api/go.mod is updated with version bumps for multiple indirect dependencies, reorganization of go-openapi submodule requirements, and removal of some unused dependencies.

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'CAPI 1.11' clearly identifies the primary objective of upgrading Cluster API to version 1.11, which is directly reflected in all three modified files (linter config, Makefile, and go.mod).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	No Ginkgo test files were modified in this PR, which only changes .golangci.yml, Makefile, and api/go.mod configuration files.
Test Structure And Quality	✅ Passed	PR contains only configuration and dependency changes (.golangci.yml, Makefile, api/go.mod) with no modifications to Ginkgo test code.
Microshift Test Compatibility	✅ Passed	This PR does not add any new Ginkgo e2e tests; it only modifies configuration and dependency files (.golangci.yml, Makefile, api/go.mod).
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This pull request does not add any new Ginkgo e2e tests. The PR only modifies three configuration and dependency files: .golangci.yml, Makefile, and api/go.mod. Since no new test definitions using Ginkgo patterns are introduced, the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR exclusively modifies build configuration and dependencies to upgrade Cluster API v1.11 without introducing scheduling constraints or topology-dependent logic.
Ote Binary Stdout Contract	✅ Passed	PR modifies only configuration and dependency files with no changes to Go source code or test files, so OTE Binary Stdout Contract cannot be violated.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only configuration and dependency files (.golangci.yml, Makefile, api/go.mod) with no new Ginkgo e2e tests added.
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 · 2026-01-27T09:56:51Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

openshift-ci-robot · 2026-01-27T16:41:50Z

openshift-ci-robot · 2026-01-27T16:44:17Z

clebs · 2026-01-29T15:24:09Z

/test e2e-aws-minimal verify

hypershift-jira-solve-ci · 2026-05-18T13:46:00Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aks | Build: 2056339374513065984 | Cost: $8.81044475 | Failed step: hypershift-azure-run-e2e

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

clebs · 2026-05-19T11:48:45Z

/retest

hypershift-jira-solve-ci · 2026-05-19T14:30:00Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aks | Build: 2056703662964609024 | Cost: $4.523801750000001 | Failed step: hypershift-azure-run-e2e

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

hypershift-jira-solve-ci · 2026-05-19T15:17:33Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aws | Build: 2056703663002357760 | Cost: $2.9365004999999997 | Failed step: hypershift-aws-run-e2e-nested

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

clebs · 2026-05-20T21:17:02Z

/test e2e-aws e2e-aks

hypershift-jira-solve-ci · 2026-05-20T23:08:10Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aks | Build: 2057209018799099904 | Cost: $4.5854485 | Failed step: hypershift-azure-run-e2e

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

hypershift-jira-solve-ci · 2026-05-21T00:02:45Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aws | Build: 2057209018832654336 | Cost: $4.983203999999999 | Failed step: hypershift-aws-run-e2e-nested

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

clebs · 2026-05-21T08:01:02Z

/test e2e-aws e2e-aks

clebs · 2026-05-21T08:45:49Z

/test e2e-aws

- Upgrade all CAPI modules to 1.11. - Update changed import paths - Silence depreciation linter errors - Update make cluster-api goal.

CAPI 1.11 defaults to v1beta2 storage. Override to v1beta1 for HyperShift compatibility. Signed-off-by: Borja Clemente <bclement@redhat.com>

Signed-off-by: Borja Clemente <bclement@redhat.com>

Remove the temporary hardocded CAPI image overrides now that hypershift supports CAPI 1.11 Signed-off-by: Borja Clemente <bclement@redhat.com>

For conversion to work, the CAPI provider needs to be able to access CRDs cluster-wide to list available versions. Signed-off-by: Borja Clemente <bclement@redhat.com>

Update TestScaleFromZero to support both CAPI 1.11+ native Status.Capacity and pre-1.11 annotation-based capacity information. In CAPI 1.11, cluster-api-provider-aws now populates Status.Capacity directly on AWSMachineTemplate, making the workaround annotations unnecessary. The HyperShift controller detects this and skips setting annotations when Status.Capacity is present. The test now: - First checks AWSMachineTemplate.Status.Capacity (CAPI 1.11+) - Falls back to MachineDeployment annotations (pre-CAPI 1.11) - Logs the capacity source for debugging This makes the test backward compatible and fixes the failure in PR openshift#7590.

Setting the MinReadySeconds default to 0 explicitly on the nodepool controller causes infinite reconciliaiton due to a lossy v1beta1 -> v1beta2 conversion and flipping value between 0 and nil. Removing the explicit setting should not have any other side effect since the zero value of the field is the same. Signed-off-by: Borja Clemente <bclement@redhat.com>

…mplete check Replace the 1-second sleep workaround for OCPBUGS-77922 with a deterministic cross-check of the v1beta2 conversion-data annotation. In CAPI v1.11+, the v1beta1 UpdatedReplicas field maps from deprecated.v1beta1.updatedReplicas rather than the native upToDateReplicas, which can transiently disagree. When v1beta1 fields indicate completion, we now verify against the authoritative v1beta2 status in the conversion-data annotation before declaring complete. Jira: https://issues.redhat.com/browse/OCPBUGS-77922 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

The word uptodate and all its casing variants are a false positive on codespell. They are defined as such in CAPI. Signed-off-by: Borja Clemente <bclement@redhat.com>

hypershift-jira-solve-ci · 2026-05-21T09:51:24Z

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aws | Build: 2057382374441750528 | Cost: $2.0682525 | Failed step: hypershift-aws-run-e2e-nested

View full analysis report

_{Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6}

clebs · 2026-05-21T10:57:02Z

/test e2e-aws e2e-aks e2e-aws-upgrade-hypershift-operator e2e-azure-self-managed e2e-kubevirt-aws-ovn-reduced

- Cleanup backwardcompat CAPI images logic - Simplify APIVersionGetter removing filtering versions to look for v1beta1 which is not necessary. Conversion just needs to obtain whichever version is registered for a given CRD. Also improved the comment to reflect the adjustment. - Use upstream constant for conversion-data annotation instead of redefining the value. - Document capi-provider sharing role with capi-manager for CRD read access. - Log an error when conversion-data annotation unmarshal fails. Signed-off-by: Borja Clemente <bclement@redhat.com> apigetter comments juanma

clebs · 2026-05-21T17:34:15Z

/test e2e-aws e2e-aks e2e-aws-upgrade-hypershift-operator e2e-azure-self-managed e2e-kubevirt-aws-ovn-reduced

clebs · 2026-05-21T20:53:26Z

/test e2e-aws

openshift-ci · 2026-05-21T22:52:31Z

@clebs: 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/prow/e2e-aks-4-21	`80d3f1f`	link	true	`/test e2e-aks-4-21`
ci/prow/e2e-aws-4-21	`80d3f1f`	link	true	`/test e2e-aws-4-21`
ci/prow/unit	`e7c06ee`	link	true	`/test unit`
ci/prow/e2e-aks-4-22	`562b85a`	link	true	`/test e2e-aks-4-22`
ci/prow/e2e-v2-gke	`06b2474`	link	false	`/test e2e-v2-gke`
ci/prow/e2e-azure-v2-self-managed	`d24e6f3`	link	false	`/test e2e-azure-v2-self-managed`
ci/prow/e2e-gke	`e5c594b`	link	false	`/test e2e-gke`

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.

enxebre · 2026-05-25T10:40:51Z

/test e2e-aws

enxebre · 2026-05-27T09:45:00Z

/close
in favour of #8594

openshift-ci · 2026-05-27T09:45:21Z

PR needs rebase.

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.

hypershift-jira-solve-ci · 2026-05-27T09:55:34Z

Now I have the complete picture. Let me write the final report:

Test Failure Analysis Complete

Job Information

Prow Job: pull-ci-openshift-hypershift-main-e2e-gke
Build ID: 2057512977162047488
PR: CNTRLPLANE-2207: Upgrade to CAPI 1.11 #7590 (CNTRLPLANE-2207: Upgrade to CAPI 1.11)
Target: e2e-gke
Duration: 2h47m43s (test phase timed out at 2h limit)
Failed Tests: 6 failures, 10 skipped, out of 38 total

Test Failure Analysis

Error

GKE Warden rejected the request: workload 'etcd' cpu requests '360m' is lower
than the Autopilot minimum required of '500m' for using pod anti affinity.

Also: TestCreateCluster/Main/EnsureMetricsForwarderWorking: kube-apiserver target
found but health=down, lastError=Get "https://10.132.0.23:9443/metrics/kube-apiserver":
context deadline exceeded

Summary

The e2e-gke job has two independent test failures, neither caused by the CAPI 1.11 bump. (1) TestCreateClusterHABreakGlassCredentials failed because GKE Autopilot's Warden admission webhook rejected the etcd StatefulSet — the HA topology requires pod anti-affinity, which triggers a GKE Autopilot minimum CPU of 500m, but etcd requests only 360m. This blocked the entire hosted control plane from bootstrapping: no etcd → no kube-apiserver → the capi-provider's availability-prober init container hung waiting for kube-apiserver:6443/readyz → the deployment stayed "unavailable" → Degraded=True. (2) TestCreateCluster/Main/EnsureMetricsForwarderWorking failed because the Prometheus target for kube-apiserver metrics via the metrics-forwarder proxy was persistently unreachable (context deadline exceeded), a Konnectivity proxy issue (502 Bad Gateway). (3) TestCreateCluster/Teardown failed because the overall 2h test timeout was reached while teardown was in progress, and GKE credentials had expired by then. Additionally, the tide "error" state is not a test failure — it indicates the PR has merge conflicts (needs-rebase).

Root Cause

Two independent, pre-existing GKE platform issues — not caused by CAPI 1.11 bump:

Failure 1: TestCreateClusterHABreakGlassCredentials — GKE Autopilot resource constraints

The HA (HighAvailability) test creates a HostedCluster with pod anti-affinity. On GKE Autopilot, using pod anti-affinity triggers a minimum CPU request of 500m per pod. The etcd StatefulSet only requests 360m CPU for its etcd container, causing GKE Warden to reject the creation:

admission webhook "warden-validating.common-webhooks.networking.gke.io" denied the request:
workload 'etcd' cpu requests '360m' is lower than the Autopilot minimum required of '500m'
for using pod anti affinity.

A second resource also failed: the router deployment requested only 50m CPU, also below the 500m minimum.

This cascading failure prevented the entire hosted control plane from starting:

etcd StatefulSet rejected → EtcdAvailable=False: StatefulSetNotFound
No etcd → kube-apiserver never deployed → KubeAPIServerAvailable=False: NotFound
capi-provider pod's init container (availability-prober) hung forever waiting for kube-apiserver:6443/readyz
capi-provider deployment reported 1 unavailable replica → Degraded=True: UnavailableReplicas
Hosted cluster never reached Available=True

The TestCreateCluster (non-HA, SingleReplica) on the same job succeeded at cluster creation — confirming this is specific to the HA anti-affinity path.

Failure 2: TestCreateCluster/Main/EnsureMetricsForwarderWorking — Konnectivity proxy 502

The metrics forwarder test timed out because Prometheus in the guest cluster couldn't scrape kube-apiserver metrics via the metrics-forwarder proxy. The konnectivity-server-local proxy returned 502 Bad Gateway errors, and subsequent attempts hit context deadline exceeded. This is a known GKE networking flake involving the Konnectivity tunnel.

Failure 3: TestCreateCluster/Teardown — Test timeout cascade

The overall test pod timed out at the 2h limit (exit code 127). Teardown was still in progress when the timeout hit, and by then GKE credentials had expired (Unauthorized errors during cluster dump and destruction).

Tide "error" state: The PR has merge conflicts (mergeStateStatus: DIRTY, label: needs-rebase). This is not a test failure.

Recommendations

Rebase the PR — The PR has merge conflicts (label needs-rebase). Rebase onto latest main to resolve the tide error state and allow CI re-runs.
Re-run e2e-gke — After rebase, trigger /retest or /test e2e-gke. The failures are pre-existing GKE platform issues, not caused by the CAPI 1.11 changes. Other jobs (e2e-aws, e2e-aks, e2e-azure-self-managed, e2e-kubevirt-aws-ovn-reduced) all passed.
File a bug for GKE HA resource constraints (if not already tracked) — The TestCreateClusterHABreakGlassCredentials test will consistently fail on GKE Autopilot because the etcd and router resource requests are below Autopilot's minimum (500m CPU) when pod anti-affinity is used. The fix would be either:
- Increase etcd/router CPU requests to ≥500m on GKE Autopilot clusters when HA topology is used
- Or skip the HA test on GKE Autopilot (the existing TestCreateCluster already validates non-HA successfully)
The EnsureMetricsForwarderWorking failure is a known GKE flake — Konnectivity proxy 502s are intermittent on GKE. No action needed beyond re-running.

Evidence

Evidence	Detail
GKE Warden rejection	`warden-validating.common-webhooks.networking.gke.io` denied etcd with `cpu requests '360m' is lower than Autopilot minimum of '500m' for pod anti affinity`
Affected workloads	etcd (360m < 500m) and router (50m < 500m)
capi-provider stuck	Pod `capi-provider-7ffc7fd55f-tvjmq` stuck in `PodInitializing` — init container `availability-prober` running indefinitely waiting for `kube-apiserver:6443/readyz`
HostedCluster conditions	`Degraded=True: UnavailableReplicas(capi-provider has 1 unavailable replicas)`, `EtcdAvailable=False: StatefulSetNotFound`, `KubeAPIServerAvailable=False: NotFound`
Metrics forwarder timeout	`kube-apiserver target found but health=down, lastError=Get "https://10.132.0.23:9443/metrics/kube-apiserver": context deadline exceeded`
Konnectivity 502	`proxy error from konnectivity-server-local:8090 while dialing 10.0.0.3:10250, code 502: 502 Bad Gateway`
Test timeout	Exit code 127, `process timed out` at 2h limit; Teardown took 4354.70s (72 min)
Tide error	PR merge state `DIRTY`/`CONFLICTING`, label `needs-rebase`
Non-HA cluster OK	`TestCreateCluster` cluster created successfully and passed `ValidateHostedCluster` (non-HA, no anti-affinity, no Warden rejection)
CPO log (BreakGlass)	Continuous `Reconciler error` with GKE Warden rejection from 18:04:30Z through entire test duration
CPO log (CreateCluster)	No Warden errors — only benign conflict retries

openshift-ci Bot added do-not-merge/needs-area do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jan 27, 2026

clebs force-pushed the capi-1.11-bump branch from 4d11673 to 655cb0c Compare January 27, 2026 16:22

clebs changed the title ~~WIP: upgrade to CAPI 1.11~~ CNTRLPLANE-2207: upgrade to CAPI 1.11 Jan 27, 2026

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 27, 2026

clebs changed the title ~~CNTRLPLANE-2207: upgrade to CAPI 1.11~~ CNTRLPLANE-2207: Upgrade to CAPI 1.11 Jan 27, 2026

clebs force-pushed the capi-1.11-bump branch from 655cb0c to 373aa44 Compare January 29, 2026 14:17

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 29, 2026

clebs force-pushed the capi-1.11-bump branch from 373aa44 to ea19f7f Compare January 29, 2026 15:22

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 29, 2026

openshift-ci Bot added the area/platform/gcp PR/issue for GCP (GCPPlatform) platform label Jan 29, 2026

clebs force-pushed the capi-1.11-bump branch from 7d32ff9 to 76f2399 Compare January 30, 2026 09:11

clebs and others added 10 commits May 21, 2026 11:44

build(deps): Upgrade to CAPI 1.11

fdb2c67

- Upgrade all CAPI modules to 1.11. - Update changed import paths - Silence depreciation linter errors - Update make cluster-api goal.

build(deps): override CAPI CRD storage version to v1beta1

0573341

CAPI 1.11 defaults to v1beta2 storage. Override to v1beta1 for HyperShift compatibility. Signed-off-by: Borja Clemente <bclement@redhat.com>

feat(capi): Add conversion webhooks for v1beta1/v1beta2

8475a9b

Signed-off-by: Borja Clemente <bclement@redhat.com>

build(deps): update vendor dependencies for CAPI 1.11

71607fc

Signed-off-by: Borja Clemente <bclement@redhat.com>

fix(capi): remove hardcoded image overrides

80a0983

Remove the temporary hardocded CAPI image overrides now that hypershift supports CAPI 1.11 Signed-off-by: Borja Clemente <bclement@redhat.com>

fix(conversion): give capi-provider access to CRDs

93d0d57

For conversion to work, the CAPI provider needs to be able to access CRDs cluster-wide to list available versions. Signed-off-by: Borja Clemente <bclement@redhat.com>

fix(codespell): Add uptodate to codespellignore

fda6a60

The word uptodate and all its casing variants are a false positive on codespell. They are defined as such in CAPI. Signed-off-by: Borja Clemente <bclement@redhat.com>

enxebre mentioned this pull request May 27, 2026

CNTRLPLANE-2207: Upgrade to CAPI 1.11 #8594

Merged

12 tasks

Conversation

clebs commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Checklist:

Summary by CodeRabbit

Release Notes

Uh oh!

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

Uh oh!

Reviews paused

Walkthrough

Uh oh!

openshift-ci Bot commented Jan 27, 2026

Uh oh!

openshift-ci-robot commented Jan 27, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Checklist:

Uh oh!

openshift-ci-robot commented Jan 27, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this PR does / why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Checklist:

Uh oh!

clebs commented Jan 29, 2026

Uh oh!

hypershift-jira-solve-ci Bot commented May 18, 2026

AI Test Failure Analysis

Uh oh!

clebs commented May 19, 2026

Uh oh!

hypershift-jira-solve-ci Bot commented May 19, 2026

AI Test Failure Analysis

Uh oh!

hypershift-jira-solve-ci Bot commented May 19, 2026

AI Test Failure Analysis

Uh oh!

clebs commented May 20, 2026

Uh oh!

hypershift-jira-solve-ci Bot commented May 20, 2026

AI Test Failure Analysis

Uh oh!

hypershift-jira-solve-ci Bot commented May 21, 2026

AI Test Failure Analysis

Uh oh!

clebs commented May 21, 2026

Uh oh!

clebs commented May 21, 2026

Uh oh!

hypershift-jira-solve-ci Bot commented May 21, 2026

AI Test Failure Analysis

Uh oh!

clebs commented May 21, 2026

Uh oh!

clebs commented May 21, 2026

Uh oh!

clebs commented May 21, 2026

Uh oh!

openshift-ci Bot commented May 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

enxebre commented May 25, 2026

Uh oh!

enxebre commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented May 27, 2026

Uh oh!

hypershift-jira-solve-ci Bot commented May 27, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Failure Analysis Complete

Job Information

Test Failure Analysis

clebs commented Jan 27, 2026 •

edited

Loading

coderabbitai Bot commented Jan 27, 2026 •

edited

Loading

openshift-ci-robot commented Jan 27, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Jan 27, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci Bot commented May 21, 2026 •

edited

Loading

enxebre commented May 27, 2026 •

edited

Loading

hypershift-jira-solve-ci Bot commented May 27, 2026 •

edited by openshift-ci Bot

Loading