Skip to content

MGMT-24397: Add OCP test version builder & PoC#10321

Open
bluesort wants to merge 1 commit into
openshift:masterfrom
bluesort:mgmt-24397
Open

MGMT-24397: Add OCP test version builder & PoC#10321
bluesort wants to merge 1 commit into
openshift:masterfrom
bluesort:mgmt-24397

Conversation

@bluesort
Copy link
Copy Markdown
Member

@bluesort bluesort commented May 12, 2026

Problem

During ACM feature freeze, older OCP versions are pruned from data files. Tests that hardcode version strings then break and require manual edits or removal to reach green CI on the version pruning PR.

Solution

Add TestVersionBuilder for resolving test versions from data files instead of hardcoding them. This API lets tests reference versions dynamically, applying any needed constraints, so they adapt when data files change via make generate.

Tests that are specific to exact versions or ranges will specify constrains and will be skipped when no matching version is present. 2 of the tests in subsystem/cluster_test.go have been updated as a PoC for this pattern.

Unit tests unnecessarily pinned to specific versions will be updated to use the latest available version or apply their own constraints and skip when no matching version is present. The shared unit test config as well as the tests in internal/releasesources/release_sources_test.go have been updated as a PoC for this pattern.

The rest of the codebase will be updated in followup branches to keep changes focused and testable.

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

Summary by CodeRabbit

  • New Features

    • Per-architecture test-version list generation now runs as part of the generation workflow.
    • Added a fluent test-version selector allowing latest/oldest selection and semantic constraints per architecture.
  • Tests

    • Test suites and default test configuration derive versions dynamically and will skip when a requested version is unavailable.
    • Updated tests to construct release-image references from resolved versions.
  • Bug Fixes

    • Fixed a test description typo ("Succeess" → "Success") and corrected JSON file terminations.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 12, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 12, 2026

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
Copy link
Copy Markdown

openshift-ci-robot commented May 12, 2026

@bluesort: This pull request references MGMT-24397 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Add TestVersionBuilder for resolving test versions from data files instead of hardcoding them

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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 added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 12, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bluesort

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 12, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 12, 2026

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

Adds generation of architecture-scoped OpenShift test versions from release-images data, a fluent Go API to select/filter versions, wires a DefaultTestVersion into test configuration, updates tests to use dynamic versions, and registers a Make target to run the generator.

Changes

Test version generation, selection API, wiring, and test updates

Layer / File(s) Summary
Make target and generator entry
hack/Makefile, hack/generate.sh
Add generate-test-versions Make target that runs ./hack/generate.sh generate_test_versions and include it in the generate prerequisites.
Generator implementation
hack/generate.sh
New generate_test_versions() reads data/default_release_images.json, groups openshift_version by cpu_architecture, normalizes (strip -multi), sorts numerically, emits internal/common/test_versions_generated.go, and runs gofmt.
Generated data map
internal/common/test_versions_generated.go
Generated testVersionsByArch map[string][]string (DO NOT EDIT) mapping arm64, multi, and x86_64 to ordered version slices.
Selection API for test versions
internal/common/test_versions.go
Add TestVersionBuilder and constructor TestVersion() with fluent methods ForArch, Latest, Oldest, LessThan, GreaterThan, Exact, TryVersion, Version, ReleaseVersion, and ReleaseImageURL; applies constraints using github.com/hashicorp/go-version, filters versions from testVersionsByArch, and remaps ARM64→AARCH64 in image URL suffixes.
Default test version wiring
internal/common/test_configuration.go
Introduce exported DefaultTestVersion = TestVersion().Latest() and derive OpenShiftVersion, ReleaseVersion, ReleaseImageURL, and RhcosImage from it (other exported constants unchanged).
Tests updated to use dynamic versions
internal/releasesources/release_sources_test.go, subsystem/cluster_test.go
Replace hard-coded OpenShift/release-version literals and release-image URLs with values from common.TestVersion() (use TryVersion/Exact, skip tests when unavailable); add fmt import and correct a test description typo.
sequenceDiagram
    participant Make as Make
    participant GenScript as hack/generate.sh
    participant Data as data/default_release_images.json
    participant GenFile as internal/common/test_versions_generated.go
    participant GoPkg as internal/common (test_versions.go)
    participant Tests as test files

    Make->>GenScript: run generate_test_versions
    GenScript->>Data: read release images data
    GenScript->>GenFile: write testVersionsByArch (generated Go)
    GenScript->>GenFile: run gofmt
    GoPkg->>GenFile: read testVersionsByArch at runtime
    Tests->>GoPkg: call TestVersion().Latest()/Exact()/ReleaseImageURL()
    GoPkg-->>Tests: return computed versions and image URLs
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error, 3 warnings)

Check name Status Explanation Resolution
Stable And Deterministic Test Names ❌ Error Test name contains dynamic loop variable. subsystem/cluster_test.go uses fmt.Sprintf with stage variable in test title, violating deterministic test name requirements. Replace dynamic test name with static string and move stage-specific logic to test body.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Structure And Quality ⚠️ Warning Tests lack proper cleanup for cluster resources, no meaningful assertion messages, and missing unit tests for TestVersionBuilder implementation. Add BeforeEach/AfterEach cleanup in vSphere Context. Add diagnostic messages to Expect() calls. Create unit tests for TestVersionBuilder covering constraints and edge cases.
Single Node Openshift (Sno) Test Compatibility ⚠️ Warning Two vSphere cluster tests in subsystem/cluster_test.go set ControlPlaneCount to 3 (MinMasterHostsNeededForInstallationInHaMode) without SNO safeguards, will fail on single-node clusters. Add [Skipped:SingleReplicaTopology] label to test names or add SNO check with exutil.IsSingleNode() and Skip()
✅ Passed checks (8 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: introducing a TestVersionBuilder and providing a proof-of-concept implementation for dynamic OCP version resolution.
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.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests were added in this PR. Only existing tests were modified to use dynamic version resolution. The check is not applicable since it only applies when new tests are added.
Topology-Aware Scheduling Compatibility ✅ Passed PR adds test infrastructure only: build targets, test helpers, and test data. No manifests, operators, controllers, or scheduling constraints present. Check not applicable.
Ote Binary Stdout Contract ✅ Passed Package init-time var initialization contains no stdout writes—only map initialization, string-returning functions, and panic (goes to stderr). No fmt.Print, init(), or logging violations detected.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed New tests use TestDualStackNetworking for IPv6 support and mocked clients with URL metadata only, not actual external pulls.
Description check ✅ Passed The PR description comprehensively covers the problem, solution, testing approach, and all required checklist items are completed.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 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 `@internal/common/test_versions.go`:
- Around line 51-55: The Find() method on TestVersionBuilder exposes a boolean
miss path but currently panics on the unknown-arch branch; update
TestVersionBuilder.Find (and the similar branch referenced around lines 83-87)
to avoid panics by returning ("", false) for any unknown/unsupported
architecture instead of calling panic, ensuring all code paths conform to the
advertised safe return contract and callers can probe availability without
crashing.
- Around line 70-81: ReleaseVersion() and ReleaseImageURL() always append ".0"
and "-<arch>" blindly, causing invalid tags for inputs like "4.11.0-multi";
update TestVersionBuilder.ReleaseVersion and ReleaseImageURL to 1) compute base
:= b.MustFind() and only append ".0" if the base has only two numeric components
(e.g., count of '.' == 1), 2) map ARM64CPUArchitecture -> AARCH64CPUArchitecture
for the arch variable as before, but only append "-<arch>" to the tag in
ReleaseImageURL if the base does not already contain a hyphen-suffix (i.e.,
strings.Contains(base, "-") == false) and the arch is non-empty; use the
existing symbols ReleaseVersion(), ReleaseImageURL(), MustFind(), arch,
ARM64CPUArchitecture, AARCH64CPUArchitecture to implement these checks.
🪄 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: 9ade2e0b-ecea-42ad-b18a-4cbd13315e0f

📥 Commits

Reviewing files that changed from the base of the PR and between babc11d and cb777de.

📒 Files selected for processing (6)
  • hack/Makefile
  • hack/generate.sh
  • internal/common/test_configuration.go
  • internal/common/test_versions.go
  • internal/common/test_versions_generated.go
  • internal/releasesources/release_sources_test.go

Comment thread internal/common/test_versions.go Outdated
Comment thread internal/common/test_versions.go
@bluesort bluesort changed the title MGMT-24397: Add test version builder MGMT-24397: Add OCP test version builder May 12, 2026
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
internal/common/test_versions.go (1)

69-80: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Release tag construction is still too rigid for already-qualified versions.

Line 70 always appends .0, and Line 79 always appends -<arch>. If the selected version already includes patch/suffix (for example x.y.z or x.y.z-multi), the tag becomes malformed.

Proposed fix
 import (
 	"fmt"
+	"strings"
 
 	"github.com/hashicorp/go-version"
 )
@@
 func (b *TestVersionBuilder) ReleaseVersion() string {
-	return b.Version() + ".0"
+	v := b.Version()
+	base := strings.TrimSuffix(v, "-multi")
+	if strings.Count(base, ".") == 1 {
+		base += ".0"
+	}
+	if strings.HasSuffix(v, "-multi") {
+		return base + "-multi"
+	}
+	return base
 }
@@
 func (b *TestVersionBuilder) ReleaseImageURL() string {
+	if b.arch == MultiCPUArchitecture {
+		return fmt.Sprintf("quay.io/openshift-release-dev/ocp-release:%s", b.ReleaseVersion())
+	}
 	suffix := b.arch
 	if suffix == ARM64CPUArchitecture {
 		suffix = AARCH64CPUArchitecture
 	}
 	return fmt.Sprintf("quay.io/openshift-release-dev/ocp-release:%s-%s", b.ReleaseVersion(), suffix)
 }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@internal/common/test_versions.go` around lines 69 - 80, The ReleaseVersion
and ReleaseImageURL helpers currently always append ".0" and "-<arch>", which
corrupts already-qualified versions like "x.y.z" or "x.y.z-multi"; update
ReleaseVersion to only append ".0" when b.Version() is a bare "major.minor"
(e.g., match something like `^\d+\.\d+$`) and otherwise return b.Version()
unchanged, and update ReleaseImageURL to build the tag from ReleaseVersion but
only append the architecture suffix when the tag does not already contain a "-"
suffix (i.e., if the tag already contains "-" or already ends with the mapped
arch string, do not add another "-<arch>"); keep the ARM64->AARCH64 mapping
logic using ARM64CPUArchitecture and AARCH64CPUArchitecture and use fmt.Sprintf
as before.
🤖 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.

Duplicate comments:
In `@internal/common/test_versions.go`:
- Around line 69-80: The ReleaseVersion and ReleaseImageURL helpers currently
always append ".0" and "-<arch>", which corrupts already-qualified versions like
"x.y.z" or "x.y.z-multi"; update ReleaseVersion to only append ".0" when
b.Version() is a bare "major.minor" (e.g., match something like `^\d+\.\d+$`)
and otherwise return b.Version() unchanged, and update ReleaseImageURL to build
the tag from ReleaseVersion but only append the architecture suffix when the tag
does not already contain a "-" suffix (i.e., if the tag already contains "-" or
already ends with the mapped arch string, do not add another "-<arch>"); keep
the ARM64->AARCH64 mapping logic using ARM64CPUArchitecture and
AARCH64CPUArchitecture and use fmt.Sprintf as before.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 1626b3a5-de76-42f3-a977-cace49fa3f45

📥 Commits

Reviewing files that changed from the base of the PR and between 260bbe8 and eb0d397.

📒 Files selected for processing (3)
  • hack/generate.sh
  • internal/common/test_versions.go
  • internal/common/test_versions_generated.go
✅ Files skipped from review due to trivial changes (1)
  • internal/common/test_versions_generated.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • hack/generate.sh

@bluesort bluesort changed the title MGMT-24397: Add OCP test version builder MGMT-24397: Add OCP test version builder & PoC May 13, 2026
@bluesort bluesort marked this pull request as ready for review May 13, 2026 18:28
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 13, 2026
@openshift-ci openshift-ci Bot requested review from giladravid16 and yoavsc0302 May 13, 2026 18:29
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 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 `@hack/Makefile`:
- Line 67: The Makefile currently defines targets named generate and
generate-test-versions that should be declared phony to avoid accidental
skipping when files with those names exist; update the Makefile by adding a
.PHONY declaration listing generate and generate-test-versions (e.g., add a line
like ".PHONY: generate generate-test-versions" near other .PHONY entries or the
top of the file) so that the generate and generate-test-versions targets are
always executed regardless of same-named files in the workspace.
🪄 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: 7795b9bb-6c76-43f4-9cf5-3d644cf26f16

📥 Commits

Reviewing files that changed from the base of the PR and between eb0d397 and 3908ca8.

📒 Files selected for processing (7)
  • hack/Makefile
  • hack/generate.sh
  • internal/common/test_configuration.go
  • internal/common/test_versions.go
  • internal/common/test_versions_generated.go
  • internal/releasesources/release_sources_test.go
  • subsystem/cluster_test.go
✅ Files skipped from review due to trivial changes (1)
  • internal/common/test_versions_generated.go
🚧 Files skipped from review as they are similar to previous changes (4)
  • hack/generate.sh
  • internal/common/test_versions.go
  • internal/releasesources/release_sources_test.go
  • internal/common/test_configuration.go

Comment thread hack/Makefile
@codecov
Copy link
Copy Markdown

codecov Bot commented May 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.37%. Comparing base (babc11d) to head (3fba3f1).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10321      +/-   ##
==========================================
+ Coverage   44.33%   44.37%   +0.03%     
==========================================
  Files         417      418       +1     
  Lines       72837    72829       -8     
==========================================
+ Hits        32294    32316      +22     
+ Misses      37609    37592      -17     
+ Partials     2934     2921      -13     
Files with missing lines Coverage Δ
internal/common/test_configuration.go 0.00% <ø> (ø)
internal/common/test_versions.go 100.00% <100.00%> (ø)

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bluesort
Copy link
Copy Markdown
Member Author

/override ci/prow/edge-e2e-ai-operator-ztp

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 13, 2026

@bluesort: Overrode contexts on behalf of bluesort: ci/prow/edge-e2e-ai-operator-ztp

Details

In response to this:

/override ci/prow/edge-e2e-ai-operator-ztp

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.

@bluesort
Copy link
Copy Markdown
Member Author

/test mce-images
/test verify-deps
/test edge-verify-generated-code

@openshift-ci openshift-ci Bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 13, 2026
@bluesort
Copy link
Copy Markdown
Member Author

bluesort commented May 15, 2026

/override ci/prow/edge-e2e-ai-operator-ztp
/override ci/prow/verify-generated-code

verify-generated-code is flaky due to its current memory limit. PR to increase is here. In the meantime, I've run the step manually on this branch to confirm no pending generated changes and am overriding

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@bluesort: Overrode contexts on behalf of bluesort: ci/prow/edge-e2e-ai-operator-ztp

Details

In response to this:

/override ci/prow/edge-e2e-ai-operator-ztp
/overried ci/prow/verify-generated-code

verify-generated-code is flaky due to its current memory limit. PR to increase is here. In the meantime, I've run the step manually on this branch to confirm no pending generated changes and am overriding

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.

@bluesort
Copy link
Copy Markdown
Member Author

typo
/override ci/prow/verify-generated-code

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@bluesort: Overrode contexts on behalf of bluesort: ci/prow/verify-generated-code

Details

In response to this:

typo
/override ci/prow/verify-generated-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 kubernetes-sigs/prow repository.

Add TestVersionBuilder for resolving test versions from data files instead of hardcoding them. These helpers let tests reference versions dynamically so they adapt when data files change via make generate.
@bluesort
Copy link
Copy Markdown
Member Author

/test edge-e2e-metal-assisted-4-22
/override ci/prow/edge-e2e-ai-operator-ztp
/test edge-e2e-metal-assisted-5-0
/test e2e-agent-compact-ipv4
/override ci/prow/verify-generated-code
/test e2e-agent-compact-ipv4-iso-no-registry

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@bluesort: Overrode contexts on behalf of bluesort: ci/prow/edge-e2e-ai-operator-ztp, ci/prow/verify-generated-code

Details

In response to this:

/test edge-e2e-metal-assisted-4-22
/override ci/prow/edge-e2e-ai-operator-ztp
/test edge-e2e-metal-assisted-5-0
/test e2e-agent-compact-ipv4
/override ci/prow/verify-generated-code
/test e2e-agent-compact-ipv4-iso-no-registry

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.

@bluesort
Copy link
Copy Markdown
Member Author

/retest

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 15, 2026

@bluesort: 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-agent-compact-ipv4-iso-no-registry 3fba3f1 link false /test e2e-agent-compact-ipv4-iso-no-registry
ci/prow/edge-e2e-metal-assisted-4-22 3fba3f1 link true /test edge-e2e-metal-assisted-4-22
ci/prow/e2e-agent-compact-ipv4 3fba3f1 link true /test e2e-agent-compact-ipv4
ci/prow/edge-e2e-metal-assisted-5-0 3fba3f1 link true /test edge-e2e-metal-assisted-5-0
ci/prow/verify-generated-code 3fba3f1 link true /test verify-generated-code

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. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants