[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042, OCPBUGS-92043, OCPBUGS-92044, OCPBUGS-92045: Backport noOLM Gateway API test coverage and upgrade tests by gcs278 · Pull Request #31322 · openshift/origin

gcs278 · 2026-06-22T21:00:04Z

Summary

Backport of Gateway API noOLM (Sail Library) test coverage and upgrade tests to release-4.20, as part of the Sail Library backport (NE-2286). This provides full test coverage for the GatewayAPIWithoutOLM feature gate, including OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes.

This is an identical backport to the 4.21 PR: #31232

Depends on #31262

Cherry-picked PRs

PR	Title	Type
#30897	NE-2561: Add Gateway API OLM to noOLM migration upgrade test	Feature
#30964	OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone	Bug fix
#31000	OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic	Bug fix
#31023	OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers	Bug fix

Add upgrade test validating Gateway API migration from OLM-based Istio to CIO-managed Sail Library during 4.21 to 4.22 upgrades. Setup creates Gateway/HTTPRoute with OLM provisioning and tests connectivity. Test validates migration: Gateway remains programmed, Istiod running, Istio CRDs stay OLM-managed, GatewayClass has CIO finalizer, Istio CR deleted, subscription persists. Teardown cleans up all resources. Cherry-picked from: cf1f826 openshift#30897

…ip logic The Gateway API upgrade test was calling g.Skip() from Setup(), which runs inside a goroutine managed by the disruption framework. Since g.Skip() panics and Ginkgo can only recover panics inside leaf nodes, this caused unrecoverable panics on IPv6/dual-stack, OKD, and unsupported platform clusters. Implement the upgrades.Skippable interface with a Skip() method that the disruption framework calls before Setup, avoiding the goroutine panic. Refactor checkPlatformSupportAndGetCapabilities into shouldSkipGatewayAPITests (safe outside Ginkgo nodes) and getPlatformCapabilities (returns LB/DNS support). https://redhat.atlassian.net/browse/OCPBUGS-83267 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Cherry-picked from: 8ef51c3 openshift#31000

The Gateway API controller tests tracked Gateways in a shared in-memory gateways slice, deleting them during AfterEach cleanup. However, openshift-tests distributes tests across separate parallel worker processes. The annotation-based checkAllTestsDone coordination works correctly because annotations are stored on the cluster-scoped GatewayClass, but the gateways slice is not shared across processes. The process that runs the final AfterEach cleanup has an empty gateways slice, so it deletes the GatewayClass and istiod but never deletes the Gateways created by other processes. This leaves gateway deployments orphaned on the cluster. As a secondary issue, even when gateways were deleted, the GatewayClass and istiod were removed without waiting for the gateway proxy deployments to be fully cleaned up by GC. Since the deployments have an owner reference to the Gateway (not a finalizer), the cascade deletion is asynchronous, creating a race where gateway pods lose their control plane and crash-loop. Fix both issues by cleaning up gateways at the individual test level using defer deleteGateway, which deletes the Gateway and waits for its proxy deployment to be removed by GC. Add deleteGateway and waitForGatewayDeploymentDeletion helpers shared by both the controller tests and the upgrade test Teardown. Cleanup errors now hard fail to surface leftover resources immediately rather than causing confusing downstream test failures. https://redhat.atlassian.net/browse/OCPBUGS-83281 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-Authored-By: Grant Spence <gspence@redhat.com> Co-Authored-By: Ishmam Amin <iamin@redhat.com> Cherry-picked from: 3f8a12d openshift#31023

Cherry-picked from: e29073f openshift#31023

Cherry-picked from: ca41c36 openshift#31023

Add retry logic to markTestDone to handle optimistic locking conflicts when updating GatewayClass annotations. The CIO actively manages the GatewayClass (updating conditions, status, finalizers) which can cause 409 Conflict errors when tests try to update annotations. Using RetryOnConflict ensures the test automatically retries with the latest resourceVersion when concurrent updates occur. Fixes flake: Operation cannot be fulfilled on gatewayclasses.gateway.networking.k8s.io "openshift-default": the object has been modified; please apply your changes to the latest version and try again https://redhat.atlassian.net/browse/OCPBUGS-81751 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Cherry-picked from: 8e4e43a openshift#30964

coderabbitai · 2026-06-22T21:00:16Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9cb97e43-1c4e-46a1-ae97-49927a0c14e6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-ci-robot · 2026-06-22T21:00:16Z

@gcs278: This pull request references Jira Issue OCPBUGS-88295, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-86778 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-82146, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-76609 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-78330, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-88300 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-85550, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-88302 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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:

Summary

Backport of Gateway API noOLM test coverage and upgrade tests from release-4.21 (#31232) to release-4.20. This adds OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes for the GatewayAPIWithoutOLM feature gate.

This is part of an approved SBAR to backport the Sail Library (noOLM) from 4.22 to 4.19–4.21.

Background

Gateway API on OCP 4.19–4.21 uses the Cluster Ingress Operator (CIO) to install Istio via OLM (OSSM operator). This path has several critical bugs:

OCPBUGS-88295: OSSM z-stream upgrades are blocked, preventing CVE fixes from being delivered

OCPBUGS-82146: OLM-related install failures

OCPBUGS-78330: Hardcoded catalog source breaks disconnected environments

OCPBUGS-85550: Gateway API fails on clusters without Marketplace capability

In OCP 4.22, NE-2286 replaced OLM with the Sail Library — CIO now installs Istio directly via embedded Helm charts. This feature shipped as GA behind the GatewayAPIWithoutOLM feature gate.

Cherry-picked PRs

PR Title

#30897 NE-2292: Add Gateway API OLM to NO-OLM migration upgrade test

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone

Rollout Plan

Phase 1 — Land code (gate OFF)

[release-4.20] OCPBUGS-85155: Backport GatewayAPIWithoutOLM feature gate as disabled api#2871 — Add FG as disabled

[release-4.20] OCPBUGS-85155, OCPBUGS-87207: Enable Gateway API tests on vSphere and baremetal #31262 — Backport Gateway API test prerequisites (baremetal/vSphere)

This PR — Backport noOLM test coverage and upgrade tests

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library cluster-ingress-operator#1459 — Sail Library code lands, gate OFF

Phase 2 — TechPreview soak

[release-4.20] NE-2480: Promote GatewayAPIWithoutOLM feature gate to TechPreview api#2874 — FG promotion to TechPreviewNoUpgrade

Verify CI soak in TP periodic jobs

Phase 3 — GA promotion

TODO: Remove feature-set annotation from Sail Library RBAC

[release-4.20] WIP: NE-2480: Promote GatewayAPIWithoutOLM feature gate to Default api#2869 — FG promotion to Default/GA, activates noOLM

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-robot · 2026-06-22T21:00:17Z

@gcs278: This pull request references Jira Issue OCPBUGS-88295, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-86778 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-82146, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-76609 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-78330, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-88300 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-85550, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-88302 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

Details

In response to this:

Summary

Backport of Gateway API noOLM test coverage and upgrade tests from release-4.21 (#31232) to release-4.20. This adds OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes for the GatewayAPIWithoutOLM feature gate.

This is part of an approved SBAR to backport the Sail Library (noOLM) from 4.22 to 4.19–4.21.

Background

Gateway API on OCP 4.19–4.21 uses the Cluster Ingress Operator (CIO) to install Istio via OLM (OSSM operator). This path has several critical bugs:

OCPBUGS-88295: OSSM z-stream upgrades are blocked, preventing CVE fixes from being delivered

OCPBUGS-82146: OLM-related install failures

OCPBUGS-78330: Hardcoded catalog source breaks disconnected environments

OCPBUGS-85550: Gateway API fails on clusters without Marketplace capability

In OCP 4.22, NE-2286 replaced OLM with the Sail Library — CIO now installs Istio directly via embedded Helm charts. This feature shipped as GA behind the GatewayAPIWithoutOLM feature gate.

Cherry-picked PRs

PR Title

#30897 NE-2292: Add Gateway API OLM to NO-OLM migration upgrade test

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone

Rollout Plan

Phase 1 — Land code (gate OFF)

[release-4.20] OCPBUGS-85155: Backport GatewayAPIWithoutOLM feature gate as disabled api#2871 — Add FG as disabled

[release-4.20] OCPBUGS-85155, OCPBUGS-87207: Enable Gateway API tests on vSphere and baremetal #31262 — Backport Gateway API test prerequisites (baremetal/vSphere)

This PR — Backport noOLM test coverage and upgrade tests

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library cluster-ingress-operator#1459 — Sail Library code lands, gate OFF

Phase 2 — TechPreview soak

[release-4.20] NE-2480: Promote GatewayAPIWithoutOLM feature gate to TechPreview api#2874 — FG promotion to TechPreviewNoUpgrade

Verify CI soak in TP periodic jobs

Phase 3 — GA promotion

TODO: Remove feature-set annotation from Sail Library RBAC

[release-4.20] WIP: NE-2480: Promote GatewayAPIWithoutOLM feature gate to Default api#2869 — FG promotion to Default/GA, activates noOLM

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 · 2026-06-22T21:00:39Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gcs278
Once this PR has been reviewed and has the lgtm label, please assign dennisperiquet 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:

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-robot · 2026-06-22T21:02:41Z

@gcs278: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Summary

Backport of Gateway API noOLM (Sail Library) test coverage and upgrade tests to release-4.20, as part of the Sail Library backport (NE-2286). This provides full test coverage for the GatewayAPIWithoutOLM feature gate, including OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes.

Depends on #31262

Cherry-picked PRs

PR Title Type

#30897 NE-2561: Add Gateway API OLM to noOLM migration upgrade test Feature

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone Bug fix

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic Bug fix

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers Bug fix

Rollout Plan

Phase 1 — Land code (gate OFF)

[release-4.20] OCPBUGS-85155: Backport GatewayAPIWithoutOLM feature gate as disabled api#2871 — Add FG as disabled

[release-4.20] OCPBUGS-85155, OCPBUGS-87207: Enable Gateway API tests on vSphere and baremetal #31262 — Backport Gateway API test prerequisites (baremetal/vSphere)

This PR — Backport noOLM test coverage and upgrade tests

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library cluster-ingress-operator#1459 — Sail Library code lands, gate OFF

Phase 2 — TechPreview soak

[release-4.20] NE-2480: Promote GatewayAPIWithoutOLM feature gate to TechPreview api#2874 — FG promotion to TechPreviewNoUpgrade

Verify CI soak in TP periodic jobs

Phase 3 — GA promotion

TODO: Remove feature-set annotation from Sail Library RBAC

[release-4.20] WIP: NE-2480: Promote GatewayAPIWithoutOLM feature gate to Default api#2869 — FG promotion to Default/GA, activates noOLM

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 · 2026-06-23T00:46:18Z

@gcs278: 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/prow/e2e-aws-ovn-upgrade-rollback	`774076f`	link	false	`/test e2e-aws-ovn-upgrade-rollback`

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.

gcs278 · 2026-06-24T16:46:21Z

/assign @rhamini3

openshift-ci-robot · 2026-06-24T17:19:19Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is invalid:

expected dependent Jira Issue OCPBUGS-88295 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92039, which is invalid:

expected dependent Jira Issue OCPBUGS-88297 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92040, which is invalid:

expected dependent Jira Issue OCPBUGS-82146 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92041, which is invalid:

expected dependent Jira Issue OCPBUGS-78330 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92042, which is invalid:

expected dependent Jira Issue OCPBUGS-85550 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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:

Summary

Backport of Gateway API noOLM (Sail Library) test coverage and upgrade tests to release-4.20, as part of the Sail Library backport (NE-2286). This provides full test coverage for the GatewayAPIWithoutOLM feature gate, including OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes.

Depends on #31262

Cherry-picked PRs

PR Title Type

#30897 NE-2561: Add Gateway API OLM to noOLM migration upgrade test Feature

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone Bug fix

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic Bug fix

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers Bug fix

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-robot · 2026-06-24T17:47:45Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is invalid:

expected dependent Jira Issue OCPBUGS-88295 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92039, which is invalid:

expected dependent Jira Issue OCPBUGS-88297 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92040, which is invalid:

expected dependent Jira Issue OCPBUGS-82146 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92041, which is invalid:

expected dependent Jira Issue OCPBUGS-78330 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92042, which is invalid:

expected dependent Jira Issue OCPBUGS-85550 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92043, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88320 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88320 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

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

This pull request references Jira Issue OCPBUGS-92044, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-83712 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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.

This pull request references Jira Issue OCPBUGS-92045, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21.z" instead
expected dependent Jira Issue OCPBUGS-84322 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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:

Summary

Backport of Gateway API noOLM (Sail Library) test coverage and upgrade tests to release-4.20, as part of the Sail Library backport (NE-2286). This provides full test coverage for the GatewayAPIWithoutOLM feature gate, including OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes.

Depends on #31262

Cherry-picked PRs

PR Title Type

#30897 NE-2561: Add Gateway API OLM to noOLM migration upgrade test Feature

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone Bug fix

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic Bug fix

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers Bug fix

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.

gcs278 · 2026-06-24T17:56:41Z

/jira refresh

openshift-ci-robot · 2026-06-24T17:56:57Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is invalid:

expected dependent Jira Issue OCPBUGS-88295 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92039, which is invalid:

expected dependent Jira Issue OCPBUGS-88297 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92040, which is invalid:

expected dependent Jira Issue OCPBUGS-82146 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92041, which is invalid:

expected dependent Jira Issue OCPBUGS-78330 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92042, which is invalid:

expected dependent Jira Issue OCPBUGS-85550 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92043, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88320 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88320 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-92044, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88322 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88322 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

This pull request references Jira Issue OCPBUGS-92045, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88324 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88324 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

Details

In response to this:

/jira refresh

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-robot · 2026-06-25T01:55:48Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is invalid:

expected dependent Jira Issue OCPBUGS-88295 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92039, which is invalid:

expected dependent Jira Issue OCPBUGS-88297 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92040, which is invalid:

expected dependent Jira Issue OCPBUGS-82146 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92041, which is invalid:

expected dependent Jira Issue OCPBUGS-78330 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92042, which is invalid:

expected dependent Jira Issue OCPBUGS-85550 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references Jira Issue OCPBUGS-92043, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88320 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88320 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-92044, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88322 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88322 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

This pull request references Jira Issue OCPBUGS-92045, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-88324 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88324 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

Details

In response to this:

Summary

Backport of Gateway API noOLM (Sail Library) test coverage and upgrade tests to release-4.20, as part of the Sail Library backport (NE-2286). This provides full test coverage for the GatewayAPIWithoutOLM feature gate, including OLM-to-Sail-Library migration upgrade testing, test flake fixes, and parallel worker cleanup fixes.

This is an identical backport to the 4.21 PR: #31232

Depends on #31262

Cherry-picked PRs

PR Title Type

#30897 NE-2561: Add Gateway API OLM to noOLM migration upgrade test Feature

#30964 OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone Bug fix

#31000 OCPBUGS-83267: Use upgrades.Skippable for Gateway API upgrade test skip logic Bug fix

#31023 OCPBUGS-83281: Fix Gateway cleanup in parallel e2e test workers Bug fix

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.

gcs278 · 2026-06-25T02:05:12Z

/testwith openshift/origin/release-4.20/e2e-gcp-ovn openshift/cluster-ingress-operator#1459 openshift/api#2869

gcs278 · 2026-06-25T02:05:19Z

/testwith openshift/origin/release-4.20/e2e-gcp-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

gcs278 · 2026-06-25T02:06:32Z

This is a subset of payload jobs that helps proves merging these tests won't break anything:

/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-aws-ovn-upgrade-out-of-change
/payload-job periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-vsphere-ovn-upgrade
/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-upgrade
/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6
/payload-job periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
/payload-job periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-upgrade-fips

openshift-ci · 2026-06-25T02:06:38Z

@gcs278: trigger 8 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.20-e2e-aws-ovn-upgrade-out-of-change
periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
periodic-ci-openshift-release-main-ci-4.20-e2e-azure-ovn-upgrade
periodic-ci-openshift-release-main-ci-4.20-e2e-vsphere-ovn-upgrade
periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-ovn-upgrade
periodic-ci-openshift-release-main-nightly-4.20-e2e-metal-ipi-upgrade-ovn-ipv6
periodic-ci-openshift-release-main-ci-4.20-e2e-aws-upgrade-ovn-single-node
periodic-ci-openshift-release-main-nightly-4.20-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7d1861c0-703a-11f1-904d-bead4ca4813c-0

gcs278 · 2026-06-25T02:10:08Z

/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:10:13Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fdb1ad50-703a-11f1-8ca6-25963c2f707b-0

gcs278 · 2026-06-25T02:10:17Z

/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:10:22Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/02cda910-703b-11f1-8202-b9ab34f52f2b-0

gcs278 · 2026-06-25T02:10:29Z

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6 openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:10:33Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/09d8a390-703b-11f1-9aa0-93a802cd5146-0

gcs278 · 2026-06-25T02:16:20Z

re-running testwith jobs because of merge conflict in FG promotion PR

gcs278 · 2026-06-25T02:16:27Z

/testwith openshift/origin/release-4.20/e2e-gcp-ovn openshift/cluster-ingress-operator#1459 openshift/api#2869

gcs278 · 2026-06-25T02:16:42Z

/testwith openshift/origin/release-4.20/e2e-gcp-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

gcs278 · 2026-06-25T02:17:15Z

/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:17:21Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fcafd840-703b-11f1-962a-ea9f67a1d4d1-0

gcs278 · 2026-06-25T02:17:32Z

/payload-job-with-prs periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:17:37Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06111ed0-703c-11f1-940d-9b8efc8783d7-0

gcs278 · 2026-06-25T02:17:49Z

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6 openshift/cluster-ingress-operator#1459 openshift/api#2869

openshift-ci · 2026-06-25T02:17:55Z

@gcs278: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/10ca2d30-703c-11f1-9e9a-43d6051ce295-0

gcs278 and others added 6 commits June 22, 2026 16:52

fail the test if it fails on test cleanup

9d832c0

Cherry-picked from: e29073f openshift#31023

update the OLM resources cleanup for non-OLM clusters

681163f

Cherry-picked from: ca41c36 openshift#31023

openshift-ci Bot requested review from p0lyn0mial and rfredette June 22, 2026 21:00

gcs278 changed the title ~~[release-4.20] OCPBUGS-88295, OCPBUGS-82146, OCPBUGS-78330, OCPBUGS-85550: Backport noOLM Gateway API test coverage and upgrade tests~~ [release-4.20] Backport noOLM Gateway API test coverage and upgrade tests Jun 22, 2026

openshift-ci Bot assigned rhamini3 Jun 24, 2026

gcs278 changed the title ~~[release-4.20] Backport noOLM Gateway API test coverage and upgrade tests~~ [release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Backport noOLM Gateway API test coverage and upgrade tests Jun 24, 2026

openshift-ci Bot requested a review from melvinjoseph86 June 24, 2026 17:57

gcs278 mentioned this pull request Jun 25, 2026

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library openshift/cluster-ingress-operator#1459

Open

3 tasks

openshift-ci Bot mentioned this pull request Jun 25, 2026

[release-4.20] WIP: NE-2480: Promote GatewayAPIWithoutOLM feature gate to Default openshift/api#2869

Draft

Uh oh!

Conversation

gcs278 commented Jun 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Cherry-picked PRs

Uh oh!

coderabbitai Bot commented Jun 22, 2026

Review skipped

Uh oh!

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

Uh oh!

Summary

Background

Cherry-picked PRs

Rollout Plan

Uh oh!

openshift-ci-robot commented Jun 22, 2026

Summary

Background

Cherry-picked PRs

Rollout Plan

Uh oh!

openshift-ci Bot commented Jun 22, 2026

Uh oh!

openshift-ci-robot commented Jun 22, 2026

Summary

Cherry-picked PRs

Rollout Plan

Uh oh!

openshift-ci Bot commented Jun 23, 2026

Uh oh!

gcs278 commented Jun 24, 2026

Uh oh!

openshift-ci-robot commented Jun 24, 2026

Summary

Cherry-picked PRs

Uh oh!

openshift-ci-robot commented Jun 24, 2026

Summary

Cherry-picked PRs

Uh oh!

gcs278 commented Jun 24, 2026

Uh oh!

openshift-ci-robot commented Jun 24, 2026

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Summary

Cherry-picked PRs

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

gcs278 commented Jun 22, 2026 •

edited

Loading

openshift-ci-robot commented Jun 22, 2026 •

edited by openshift-ci Bot

Loading