Skip to content

OPRUN-4612: Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint#1327

Open
perdasilva wants to merge 1 commit into
openshift:mainfrom
perdasilva:custom-schema-ote
Open

OPRUN-4612: Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint#1327
perdasilva wants to merge 1 commit into
openshift:mainfrom
perdasilva:custom-schema-ote

Conversation

@perdasilva

@perdasilva perdasilva commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds E2E tests for the new api.ExperimentalRegistry/ExperimentalListPackageCustomSchemas streaming gRPC endpoint introduced in operator-registry#1981
  • Builds custom FBC catalog images in-cluster using the opm base image from the catalog-operator deployment, following the opm-example.Dockerfile pattern (pre-populated cache with --cache-only)
  • Tests the endpoint via port-forward to the CatalogSource pod using a lightweight Go gRPC client (protowire request encoding + structpb.Struct response decoding, no operator-registry dependency)

Test scenarios

  • Schema + package returns expected custom schema FBC blobs (multiple results)
  • Schema + nonexistent package returns empty stream
  • Nonexistent schema returns empty stream
  • Schema + empty package returns packageless custom schema blobs
  • Missing x-acknowledge-experimental header returns empty stream

Test plan

  • make bindata && make build && make update-metadata && make verify — all pass
  • Ran against a live OpenShift cluster — all 5 scenarios pass (110s total)

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Tests
    • Added an end-to-end test suite for the OLMv0 custom schema gRPC endpoint, validating expected results for valid schema/package queries and confirming empty results for missing packages/schemas and when the experimental header is omitted.
    • Added a new OLMv0 blocking test-case entry for the custom schema gRPC endpoint.
    • Added supporting custom-schema fixtures, including OLM index data and templates used to build a test catalog image.
  • Chores
    • Updated module dependency declarations.

@perdasilva perdasilva changed the title Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint NO-ISSUE: Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint Jun 12, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 12, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@perdasilva: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

  • Adds E2E tests for the new api.ExperimentalRegistry/ExperimentalListPackageCustomSchemas streaming gRPC endpoint introduced in operator-registry#1981
  • Builds custom FBC catalog images in-cluster using the opm base image from the catalog-operator deployment, following the opm-example.Dockerfile pattern (pre-populated cache with --cache-only)
  • Tests the endpoint via port-forward to the CatalogSource pod using a lightweight Go gRPC client (protowire request encoding + structpb.Struct response decoding, no operator-registry dependency)

Test scenarios

  • Schema + package returns expected custom schema FBC blobs (multiple results)
  • Schema + nonexistent package returns empty stream
  • Nonexistent schema returns empty stream
  • Schema + empty package returns packageless custom schema blobs
  • Missing x-acknowledge-experimental header returns empty stream

Test plan

  • make bindata && make build && make update-metadata && make verify — all pass
  • Ran against a live OpenShift cluster — all 5 scenarios pass (110s total)

🤖 Generated with Claude Code

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 openshift-ci Bot requested review from bentito and grokspawn June 12, 2026 15:55
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 12, 2026
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 6225a9d2-39c6-48fb-b1c3-f347cbc2a91c

📥 Commits

Reviewing files that changed from the base of the PR and between 5bd2a37 and 643a139.

📒 Files selected for processing (8)
  • tests-extension/.openshift-tests-extension/openshift_payload_olmv0.json
  • tests-extension/go.mod
  • tests-extension/pkg/bindata/qe/bindata.go
  • tests-extension/test/qe/specs/olmv0_custom_schema.go
  • tests-extension/test/qe/testdata/custom-schema/index.json
  • tests-extension/test/qe/testdata/olm/custom-schema-buildconfig.yaml
  • tests-extension/test/qe/testdata/olm/custom-schema-imagestream.yaml
  • tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go
✅ Files skipped from review due to trivial changes (2)
  • tests-extension/pkg/bindata/qe/bindata.go
  • tests-extension/go.mod
🚧 Files skipped from review as they are similar to previous changes (5)
  • tests-extension/test/qe/testdata/olm/custom-schema-imagestream.yaml
  • tests-extension/.openshift-tests-extension/openshift_payload_olmv0.json
  • tests-extension/test/qe/testdata/olm/custom-schema-buildconfig.yaml
  • tests-extension/test/qe/specs/olmv0_custom_schema.go
  • tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go

Walkthrough

This PR adds end-to-end testing for OLMv0 custom schema gRPC endpoints. It establishes gRPC as a direct dependency, embeds test fixtures in bindata, implements utilities for in-cluster catalog image building and gRPC port forwarding with a custom codec, and defines a test suite that validates custom schema queries across multiple scenarios including the requirement for the experimental header.

Changes

Custom Schema gRPC Testing

Layer / File(s) Summary
Dependencies and test payload registration
tests-extension/go.mod, .openshift-tests-extension/openshift_payload_olmv0.json
Move google.golang.org/grpc and google.golang.org/protobuf from indirect to direct dependencies; register new custom schema gRPC test case in OpenShift test payload as a blocking Extended test with NonHyperShiftHOST label.
Test fixtures and bindata asset embedding
test/qe/testdata/custom-schema/index.json, test/qe/testdata/olm/custom-schema-buildconfig.yaml, test/qe/testdata/olm/custom-schema-imagestream.yaml, pkg/bindata/qe/bindata.go
Create OLM catalog index with package, channel, bundle, and custom metadata entries; define parameterized OpenShift BuildConfig and ImageStream templates; generate embedded bindata asset code with byte-slice payloads, accessor functions, registry entries, and bintree hierarchy for runtime asset resolution.
gRPC codec, request encoding, and connectivity utilities
test/qe/util/olmv0util/custom_schema_grpc.go
Implement custom gRPC codec for raw request and struct response marshaling; add protobuf request encoding for custom schema queries; discover OPM base image from catalog-operator Deployment with fallback chain; implement in-cluster catalog image building that applies templates, writes FBC, generates Dockerfile with opm serve and cache pre-warm, starts binary build, and polls until Complete; add port-forwarding utility that discovers catalog pod, binds ephemeral port, and waits for readiness; provide gRPC streaming clients with optional experimental header support and error wrapping across all phases.
E2E test suite
test/qe/specs/olmv0_custom_schema.go
Define Ginkgo test suite with per-spec setup/teardown that initializes cluster context, skips unsupported environments, and manages IR resource cleanup; implement slow test that builds custom catalog image with FBC fixture, deploys CatalogSource via gRPC, port-forwards to endpoint, queries custom schemas across valid packages, nonexistent schema/package, and packageless scenarios, validates experimental header requirement, and performs all operations within 60-second timeout.

Sequence Diagrams

sequenceDiagram
  participant Test as E2E Test
  participant OPMUtil as OPM Utilities
  participant BuildAPI as Build API
  participant CatalogPod as Catalog Pod
  participant gRPCNet as gRPC Network
  Test->>OPMUtil: GetOPMBaseImage()
  OPMUtil-->>Test: base image
  Test->>BuildAPI: BuildCustomCatalogImage()
  BuildAPI->>BuildAPI: Apply templates, write FBC,<br/>generate Dockerfile
  BuildAPI->>BuildAPI: Start build & poll until Complete
  BuildAPI-->>Test: image reference
  Test->>CatalogPod: PortForwardToCatalogPod()
  CatalogPod->>CatalogPod: Discover pod, bind port,<br/>wait for readiness
  CatalogPod-->>Test: localhost:port
  Test->>gRPCNet: ListPackageCustomSchemas()
  gRPCNet->>CatalogPod: insecure gRPC, custom codec
  gRPCNet->>CatalogPod: ExperimentalListPackageCustomSchemasRequest
  CatalogPod-->>gRPCNet: structpb.Struct stream
  gRPCNet->>gRPCNet: convert & aggregate results
  gRPCNet-->>Test: map[string]interface{} results
  Test->>gRPCNet: ListPackageCustomSchemasWithoutExperimentalHeader()
  gRPCNet-->>Test: empty results (header required)
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 13 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Ipv6 And Disconnected Network Test Compatibility ⚠️ Warning Test uses hardcoded IPv4 localhost (127.0.0.1) in net.Listen() call (line 215 of custom_schema_grpc.go), which will fail in IPv6-only disconnected environments. Change net.Listen("tcp", "127.0.0.1:0") to net.Listen("tcp", "localhost:0") or net.Listen("tcp", "[::1]:0") to support IPv6, or use a dual-stack approach with fallback.
✅ Passed checks (13 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: adding E2E tests for the ExperimentalListPackageCustomSchemas gRPC endpoint, which aligns with the comprehensive test implementation across all modified files.
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 Test names are entirely static and deterministic. Describe block uses "[sig-operator][Jira:OLM] OLMv0 custom schema gRPC endpoint" and It block uses "ExperimentalListPackageCustomSchemas returns cu...
Test Structure And Quality ✅ Passed Test follows all five quality requirements: (1) single responsibility via [Slow] tag for E2E test with 5 related scenarios; (2) proper BeforeEach/AfterEach with resource cleanup via DescriberResour...
Microshift Test Compatibility ✅ Passed The test uses MicroShift-incompatible APIs (BuildConfig, ImageStream, CatalogSource) but is already protected by exutil.SkipMicroshift(oc) call in BeforeEach, which skips the test on MicroShift clu...
Single Node Openshift (Sno) Test Compatibility ✅ Passed The test makes no multi-node or HA cluster assumptions. All operations (BuildConfig, ImageStream, CatalogSource, port-forward, gRPC queries) run on a single pod in a single namespace and are compat...
Topology-Aware Scheduling Compatibility ✅ Passed PR adds test infrastructure for gRPC endpoint testing. No deployment manifests or controllers with scheduling constraints are introduced. Test case is properly marked with NonHyperShiftHOST label a...
Ote Binary Stdout Contract ✅ Passed No process-level stdout violations found. All logging uses e2e.Logf (routes to GinkgoWriter), all CLI commands buffer output, and exec stdout is properly consumed via pipes and logged via e2e.Logf.
No-Weak-Crypto ✅ Passed No weak crypto (MD5/SHA1/DES/RC4/3DES/Blowfish/ECB), custom crypto implementations, or unsafe secret comparisons found. Uses only standard libraries for gRPC and protobuf.
Container-Privileges ✅ Passed No privileged container settings, host access (hostPID/Network/IPC), SYS_ADMIN capabilities, root escalation, or allowPrivilegeEscalation flags found in YAML manifests, test files, or generated code.
No-Sensitive-Data-In-Logs ✅ Passed All logging in the PR contains only non-sensitive test data: container images, pod names, gRPC addresses, build status. No passwords, tokens, API keys, PII, session IDs, or customer data are exposed.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Biome (2.5.0)
tests-extension/test/qe/testdata/custom-schema/index.json

File contains syntax errors that prevent linting: Line 2: End of file expected; Line 3: End of file expected; Line 4: End of file expected; Line 5: End of file expected; Line 6: End of file expected


Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🤖 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.

Inline comments:
In `@tests-extension/.openshift-tests-extension/openshift_payload_olmv0.json`:
- Around line 645-659: The "name" field in the JSON entry currently contains a
placeholder Polarion ID ("PolarionID:XXXXX"); replace "XXXXX" with the actual
Polarion case identifier in the "name" value (e.g., PolarionID:12345 or your
project's canonical Polarion format) so downstream test tracking can correlate
this payload entry; update the string that begins with "[sig-operator][Jira:OLM]
OLMv0 custom schema gRPC endpoint PolarionID:XXXXX-..." to include the real ID
and verify the final name still follows existing naming conventions and escaping
(no extra brackets or quotes).

In `@tests-extension/test/qe/specs/olmv0_custom_schema.go`:
- Around line 43-53: The logs currently print full image references (baseImage
and imageRef) which can expose internal hostnames; update the logging around
olmv0util.GetOPMBaseImage (baseImage) and olmv0util.BuildCustomCatalogImage
(imageRef) to avoid emitting full refs — instead log the catalogName or a
redacted form (e.g., strip registry/host portion or replace with
"<redacted-registry>") and include contextual text; change the two e2e.Logf
calls that reference baseImage and imageRef to print only the safe identifier or
redacted string.
- Line 38: The test title string in the g.It call currently uses the placeholder
"PolarionID:XXXXX" — update that placeholder to the actual Polarion case ID
(e.g. replace "PolarionID:XXXXX" with "PolarionID:12345" or the correct
alphanumeric ID) while leaving the rest of the description
("-[Skipped:Disconnected]ExperimentalListPackageCustomSchemas returns custom
schema FBC [Slow]") intact so the test title meets the required
"PolarionID:xxxxx" format.

In `@tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go`:
- Around line 218-249: The port-forward readiness logic only watches scanner
output and a 30s timer, so early failures from cmd (exec.Command/Start) or
scanner errors are hidden; modify the code that creates and starts the
port-forward (the cmd variable and its Start call) to use a context (derive ctx
with timeout) and bind cmd to that context, and add channels to capture
cmd.Wait() errors and scanner.Scan() errors (e.g., an errCh alongside ready)
then change the select to wait on ready, errCh (receiving scanner or cmd.Wait
errors) and the time.After case so failures are surfaced immediately with the
real error instead of a generic timeout. Ensure you still kill/cleanup the
process on errors/timeouts.
- Around line 122-190: Change BuildCustomCatalogImage to accept a
context.Context and return an error instead of hard-asserting inside it: remove
o.Expect(...) calls and propagate errors from ApplyResourceFromTemplate,
os.MkdirTemp, os.WriteFile, the start-build Output() call, and the
wait.PollUntilContextTimeout call by returning them to the caller; use the
passed-in ctx for polling/timeout (replace wait.PollUntilContextTimeout with a
ctx-aware wait call, e.g., wait.PollUntilContext or use context.WithTimeout(ctx,
...)) and for any command execution
(oc.AsAdmin().WithoutNamespace().Run(...)).Output() error handling so the caller
can register cleanup before invoking BuildCustomCatalogImage and can
cancel/timeout the whole build lifecycle.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 716dc4ad-8e46-4b1c-b239-87cc49d6a8a2

📥 Commits

Reviewing files that changed from the base of the PR and between 3eb1354 and a1949bc.

📒 Files selected for processing (8)
  • tests-extension/.openshift-tests-extension/openshift_payload_olmv0.json
  • tests-extension/go.mod
  • tests-extension/pkg/bindata/qe/bindata.go
  • tests-extension/test/qe/specs/olmv0_custom_schema.go
  • tests-extension/test/qe/testdata/custom-schema/index.json
  • tests-extension/test/qe/testdata/olm/custom-schema-buildconfig.yaml
  • tests-extension/test/qe/testdata/olm/custom-schema-imagestream.yaml
  • tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go

Comment thread tests-extension/test/qe/specs/olmv0_custom_schema.go Outdated
Comment thread tests-extension/test/qe/specs/olmv0_custom_schema.go
Comment thread tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go
Comment thread tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go Outdated
@perdasilva perdasilva force-pushed the custom-schema-ote branch 2 times, most recently from 86b18e6 to 5bd2a37 Compare June 15, 2026 14:04
@perdasilva

Copy link
Copy Markdown
Contributor Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-4.22-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1 5

@perdasilva perdasilva changed the title NO-ISSUE: Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint OPRUN-4612: Add E2E tests for ExperimentalListPackageCustomSchemas gRPC endpoint Jun 15, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 15, 2026

Copy link
Copy Markdown

@perdasilva: This pull request references OPRUN-4612 which is a valid jira issue.

Details

In response to this:

Summary

  • Adds E2E tests for the new api.ExperimentalRegistry/ExperimentalListPackageCustomSchemas streaming gRPC endpoint introduced in operator-registry#1981
  • Builds custom FBC catalog images in-cluster using the opm base image from the catalog-operator deployment, following the opm-example.Dockerfile pattern (pre-populated cache with --cache-only)
  • Tests the endpoint via port-forward to the CatalogSource pod using a lightweight Go gRPC client (protowire request encoding + structpb.Struct response decoding, no operator-registry dependency)

Test scenarios

  • Schema + package returns expected custom schema FBC blobs (multiple results)
  • Schema + nonexistent package returns empty stream
  • Nonexistent schema returns empty stream
  • Schema + empty package returns packageless custom schema blobs
  • Missing x-acknowledge-experimental header returns empty stream

Test plan

  • make bindata && make build && make update-metadata && make verify — all pass
  • Ran against a live OpenShift cluster — all 5 scenarios pass (110s total)

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Tests
  • Added an end-to-end test suite covering the OLMv0 custom schema gRPC endpoint, including validation for valid schema/package queries and expected empty results for missing or omitted experimental headers.
  • Added supporting test fixtures and templates (catalog image buildconfig, imagestream, and custom-schema index data).
  • Extended bundled test assets to include the new custom-schema templates and index.
  • Added a new test-case entry to the OLMv0 payload for “OLMv0 custom schema gRPC endpoint”.
  • Chores
  • Updated module dependency declarations.

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.

@perdasilva

Copy link
Copy Markdown
Contributor Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1 5

@openshift-ci

openshift-ci Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5e4bb090-6968-11f1-8793-d0e475f5b38e-0

@pedjak pedjak left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2026

@fgiudici fgiudici left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Comment thread tests-extension/test/qe/specs/olmv0_custom_schema.go Outdated
Comment thread tests-extension/test/qe/util/olmv0util/custom_schema_grpc.go Outdated
Add tests for the new api.ExperimentalRegistry gRPC endpoint introduced
in operator-registry PR #1981. The tests build a custom FBC catalog image
in-cluster (using the opm base image from the catalog-operator deployment),
create a CatalogSource, and query the endpoint via port-forward.

Test scenarios:
- Schema + package returns expected custom schema FBC blobs
- Schema + nonexistent package returns empty stream
- Nonexistent schema returns empty stream
- Schema + empty package returns packageless blobs
- Missing x-acknowledge-experimental header returns empty stream

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Per G. da Silva <pegoncal@redhat.com>
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 18, 2026

@fgiudici fgiudici left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 18, 2026
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgiudici, perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@perdasilva

Copy link
Copy Markdown
Contributor Author

/retest

@perdasilva

Copy link
Copy Markdown
Contributor Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@perdasilva: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@perdasilva

Copy link
Copy Markdown
Contributor Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1 5

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/80e2a970-6b06-11f1-982e-48bf0d2c8aae-0

@perdasilva

Copy link
Copy Markdown
Contributor Author

/retest

@perdasilva

Copy link
Copy Markdown
Contributor Author

/payload-aggregate periodic-ci-openshift-operator-framework-olm-release-5.0-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1 5

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-operator-framework-olm-release-5.0-periodics-e2e-gcp-ovn-ipi-disconnected-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/015222e0-6b28-11f1-9caf-7b16c2a0784f-0

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@perdasilva: 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-upgrade 643a139 link true /test e2e-upgrade
ci/prow/e2e-aws-upgrade-ovn-single-node 643a139 link false /test e2e-aws-upgrade-ovn-single-node

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants