Skip to content

OCPBUGS-99768: fix OSImageStream e2e test and Makefile test-changed for OCP 5.0 - #9115

Open
bryan-cox wants to merge 2 commits into
openshift:mainfrom
bryan-cox:fix-gke-e2e
Open

OCPBUGS-99768: fix OSImageStream e2e test and Makefile test-changed for OCP 5.0#9115
bryan-cox wants to merge 2 commits into
openshift:mainfrom
bryan-cox:fix-gke-e2e

Conversation

@bryan-cox

@bryan-cox bryan-cox commented Jul 25, 2026

Copy link
Copy Markdown
Member

What this PR does / why we need it:

The NodePoolOSImageStreamDefaultStatusTest hardcoded expectedStream to rhel-9 for all OCP versions. On OCP >= 5.0, nodes run RHCOS 10 and report rhel-10 in Machine.NodeInfo.OSImage, so the controller correctly sets status.osImageStream.name to rhel-10. The hardcoded expectation caused the test to timeout waiting for a value that would never appear, breaking the e2e-v2-gke job.

The fix uses the same version-aware pattern already established in NodePoolOSImageStreamExplicitDefaultNoRolloutTest: expect rhel-9 on OCP < 5.0 and rhel-10 on OCP >= 5.0.

The test passed on PR #9033 (July 23) because the 5.0.0-0.ci nightly resolved to the July 20 build (5.0.0-0.ci-2026-07-20-122541), whose RHCOS still reported rhel-9 in NodeInfo.OSImage. By the time PR #9086 ran (July 25), the nightly resolved to the July 22 build (5.0.0-0.ci-2026-07-22-191603), which ships RHCOS 10 and reports rhel-10. The RHCOS image in the 5.0 payload flipped from RHEL 9 to RHEL 10 between July 20 and July 22.

Additionally, the test-changed Makefile target (used by the pre-push hook) failed on packages gated behind build tags like e2ev2. This PR adds a go list filter to dynamically skip packages that aren't compilable under default build constraints.

Example failing run: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9086/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080933767463047168/

Last passing run (PR #9033): https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9033/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080172889335664640/

Which issue(s) this PR fixes:

Fixes e2e-v2-gke permafail on [Feature:NodePoolOSImageStream] test

Special notes for your reviewer:

The controller behavior is correct — setOSImageStreamStatus() reads actual Machine.NodeInfo.OSImage and faithfully reports the RHEL generation the nodes are running. The test was hardcoded to expect rhel-9 regardless of OCP version, with a TODO comment (CNTRLPLANE-3032) acknowledging it needed updating. This PR implements that TODO.

Checklist:

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

Summary by CodeRabbit

  • Tests
    • Updated end-to-end validation to expect the default OS image stream derived from the OpenShift version when no value is set.
    • Improved changed-test detection to derive affected Go packages from the git diff and run tests only for resolvable, applicable packages.
    • Tests now skip cleanly when there are no relevant Go package changes.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 25, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bryan-cox: This pull request explicitly references no jira issue.

Details

In response to this:

What this PR does / why we need it:

The NodePoolOSImageStreamDefaultStatusTest hardcoded expectedStream to rhel-9 for all OCP versions. On OCP >= 5.0, nodes run RHCOS 10 and report rhel-10 in Machine.NodeInfo.OSImage, so the controller correctly sets status.osImageStream.name to rhel-10. The hardcoded expectation caused the test to timeout waiting for a value that would never appear, breaking the e2e-v2-gke job.

The fix uses the same version-aware pattern already established in NodePoolOSImageStreamExplicitDefaultNoRolloutTest: expect rhel-9 on OCP < 5.0 and rhel-10 on OCP >= 5.0.

Example failing run: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9086/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080933767463047168/

Which issue(s) this PR fixes:

Fixes e2e-v2-gke permafail on [Feature:NodePoolOSImageStream] test

Special notes for your reviewer:

The controller behavior is correct — setOSImageStreamStatus() reads actual Machine.NodeInfo.OSImage and faithfully reports the RHEL generation the nodes are running. The test was simply hardcoded to expect rhel-9 regardless of OCP version, with a TODO comment (CNTRLPLANE-3032) acknowledging it needed updating. This PR implements that TODO.

Checklist:

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

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 commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

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 openshift-ci Bot added do-not-merge/needs-area area/testing Indicates the PR includes changes for e2e testing labels Jul 25, 2026
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

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

Use the following commands to manage reviews:

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

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Updated NodePoolOSImageStreamDefaultStatusTest to validate version-derived defaults: rhel-9 for OCP versions below 5.0 and rhel-10 for OCP 5.0 and later. The test-changed Makefile target now filters changed Go directories, resolves testable packages, skips empty selections, and runs tests only for resolved packages.

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the PR’s main changes: the OSImageStream e2e test update and the Makefile test-changed adjustment for OCP 5.0.
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 All Ginkgo titles in the changed test file are static string literals; no generated names, timestamps, node/namespace/IP values, or interpolation appear in test titles.
Test Structure And Quality ✅ Passed Only Makefile changed in this commit; no Ginkgo test blocks were modified, so the test-structure checklist is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only a test and Makefile were changed; no manifests, controllers, affinities, nodeSelectors, replicas, or PDBs were added or modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The changed Ginkgo test only inspects NodePool/CRD state and uses version checks; it has no IPv4 literals, IP parsing, or external connectivity.
No-Weak-Crypto ✅ Passed The touched test and Makefile changes contain no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret/token comparisons.
Container-Privileges ✅ Passed PR only changes a Go e2e test and Makefile; no container/K8s manifests or privilege settings were added or modified.
No-Sensitive-Data-In-Logs ✅ Passed The PR diff only changes Makefile test selection logic and generic echoes; no added logs expose secrets, PII, hostnames, or customer data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci

openshift-ci Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox

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 Jul 25, 2026
@codecov

codecov Bot commented Jul 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.51%. Comparing base (872a7e8) to head (cc60bc4).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9115   +/-   ##
=======================================
  Coverage   44.51%   44.51%           
=======================================
  Files         774      774           
  Lines       96997    96997           
=======================================
  Hits        43179    43179           
  Misses      50830    50830           
  Partials     2988     2988           
Flag Coverage Δ
cmd-support 38.39% <ø> (ø)
cpo-hostedcontrolplane 47.22% <ø> (ø)
cpo-other 45.25% <ø> (ø)
hypershift-operator 54.45% <ø> (ø)
other 32.64% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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 `@Makefile`:
- Around line 393-396: Keep the CHANGED_DIRS assignment and its following if
conditional in the same shell by adding the required recipe line continuation at
the end of the assignment command. Preserve the existing changed-directory
filtering and conditional behavior so CHANGED_DIRS remains available when
evaluated.
- Around line 399-403: Update the CHANGED_PKGS package-discovery loop in the
Makefile so go list failures are no longer universally suppressed or treated as
excluded packages. Distinguish packages omitted solely by build constraints from
genuine loading errors, surface the latter, and make the test target fail when
they occur while preserving the skip behavior for constraint-only exclusions.
🪄 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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e6e3095e-7335-4593-a50a-d229bbe5ba4e

📥 Commits

Reviewing files that changed from the base of the PR and between 36c3134 and e259968.

📒 Files selected for processing (1)
  • Makefile

Comment thread Makefile
Comment thread Makefile Outdated
@bryan-cox bryan-cox changed the title NO-JIRA: fix(e2e): make OSImageStream default status test version-aware OCPBUGS-99768: fix OSImageStream e2e test and Makefile test-changed for OCP 5.0 Jul 25, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bryan-cox: This pull request references Jira Issue OCPBUGS-99768, which is invalid:

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

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

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

Details

In response to this:

What this PR does / why we need it:

The NodePoolOSImageStreamDefaultStatusTest hardcoded expectedStream to rhel-9 for all OCP versions. On OCP >= 5.0, nodes run RHCOS 10 and report rhel-10 in Machine.NodeInfo.OSImage, so the controller correctly sets status.osImageStream.name to rhel-10. The hardcoded expectation caused the test to timeout waiting for a value that would never appear, breaking the e2e-v2-gke job.

The fix uses the same version-aware pattern already established in NodePoolOSImageStreamExplicitDefaultNoRolloutTest: expect rhel-9 on OCP < 5.0 and rhel-10 on OCP >= 5.0.

The test passed on PR #9033 (July 23) because the 5.0.0-0.ci nightly resolved to the July 20 build (5.0.0-0.ci-2026-07-20-122541), whose RHCOS still reported rhel-9 in NodeInfo.OSImage. By the time PR #9086 ran (July 25), the nightly resolved to the July 22 build (5.0.0-0.ci-2026-07-22-191603), which ships RHCOS 10 and reports rhel-10. The RHCOS image in the 5.0 payload flipped from RHEL 9 to RHEL 10 between July 20 and July 22.

Additionally, the test-changed Makefile target (used by the pre-push hook) failed on packages gated behind build tags like e2ev2. This PR adds a go list filter to dynamically skip packages that aren't compilable under default build constraints.

Example failing run: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9086/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080933767463047168/

Last passing run (PR #9033): https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9033/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080172889335664640/

Which issue(s) this PR fixes:

Fixes e2e-v2-gke permafail on [Feature:NodePoolOSImageStream] test

Special notes for your reviewer:

The controller behavior is correct — setOSImageStreamStatus() reads actual Machine.NodeInfo.OSImage and faithfully reports the RHEL generation the nodes are running. The test was hardcoded to expect rhel-9 regardless of OCP version, with a TODO comment (CNTRLPLANE-3032) acknowledging it needed updating. This PR implements that TODO.

Checklist:

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

Summary by CodeRabbit

  • Tests
  • Updated end-to-end validation to expect the default OS image stream based on the OpenShift version.
  • Improved changed-test detection so only resolvable, affected Go packages are tested.
  • Tests now skip cleanly when no applicable Go packages are changed.

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.

@bryan-cox

Copy link
Copy Markdown
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bryan-cox: This pull request references Jira Issue OCPBUGS-99768, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
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

Copy link
Copy Markdown

@bryan-cox: This pull request references Jira Issue OCPBUGS-99768, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

What this PR does / why we need it:

The NodePoolOSImageStreamDefaultStatusTest hardcoded expectedStream to rhel-9 for all OCP versions. On OCP >= 5.0, nodes run RHCOS 10 and report rhel-10 in Machine.NodeInfo.OSImage, so the controller correctly sets status.osImageStream.name to rhel-10. The hardcoded expectation caused the test to timeout waiting for a value that would never appear, breaking the e2e-v2-gke job.

The fix uses the same version-aware pattern already established in NodePoolOSImageStreamExplicitDefaultNoRolloutTest: expect rhel-9 on OCP < 5.0 and rhel-10 on OCP >= 5.0.

The test passed on PR #9033 (July 23) because the 5.0.0-0.ci nightly resolved to the July 20 build (5.0.0-0.ci-2026-07-20-122541), whose RHCOS still reported rhel-9 in NodeInfo.OSImage. By the time PR #9086 ran (July 25), the nightly resolved to the July 22 build (5.0.0-0.ci-2026-07-22-191603), which ships RHCOS 10 and reports rhel-10. The RHCOS image in the 5.0 payload flipped from RHEL 9 to RHEL 10 between July 20 and July 22.

Additionally, the test-changed Makefile target (used by the pre-push hook) failed on packages gated behind build tags like e2ev2. This PR adds a go list filter to dynamically skip packages that aren't compilable under default build constraints.

Example failing run: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9086/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080933767463047168/

Last passing run (PR #9033): https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_hypershift/9033/pull-ci-openshift-hypershift-main-e2e-v2-gke/2080172889335664640/

Which issue(s) this PR fixes:

Fixes e2e-v2-gke permafail on [Feature:NodePoolOSImageStream] test

Special notes for your reviewer:

The controller behavior is correct — setOSImageStreamStatus() reads actual Machine.NodeInfo.OSImage and faithfully reports the RHEL generation the nodes are running. The test was hardcoded to expect rhel-9 regardless of OCP version, with a TODO comment (CNTRLPLANE-3032) acknowledging it needed updating. This PR implements that TODO.

Checklist:

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

Summary by CodeRabbit

  • Tests
  • Updated end-to-end validation to expect the default OS image stream derived from the OpenShift version when no value is set.
  • Improved changed-test detection to derive affected Go packages from the git diff and run tests only for resolvable, applicable packages.
  • Tests now skip cleanly when there are no relevant Go package changes.

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.

@bryan-cox

Copy link
Copy Markdown
Member Author

/test e2e-v2-gke
/test e2e-v2-aws
/test e2e-azure-v2-self-managed

bryan-cox and others added 2 commits July 25, 2026 14:36
The NodePoolOSImageStreamDefaultStatusTest hardcoded expectedStream to
rhel-9, which broke when the OCP 5.0 nightly payload switched RHCOS
from RHEL 9 to RHEL 10 (July 20-22 builds). The original fix used the
OCP release version to predict the RHEL generation, but during
transitions the payload's RHCOS version may not match the OCP minor
version (e.g. 5.0 payload with RHEL 9 RHCOS on AWS).

Instead of predicting, assert that status.osImageStream is set to any
recognized stream (rhel-9 or rhel-10). For the no-rollout test, read
the actual stream from status rather than deriving it from the version.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@bryan-cox

Copy link
Copy Markdown
Member Author

AWS e2e failure root cause

The initial fix used e2eutil.IsGreaterThanOrEqualTo(Version50) to predict rhel-10 for OCP 5.0 payloads. This worked on GKE but failed on AWS because the OCP 5.0 nightly payload on AWS still ships RHEL 9 RHCOS — the RHCOS RHEL generation transition doesn't happen uniformly across platforms.

The CI release image for this PR is built from main which targets OCP 5.0, so releaseVersion is 5.0.0, but the actual RHCOS on AWS nodes reports Red Hat Enterprise Linux CoreOS 419.x (RHEL 9). The version-based prediction is fundamentally unreliable during RHCOS transitions.

Changes made

Made the test payload-agnostic — assert the stream is set and recognized rather than predicting the exact value:

  1. NodePoolOSImageStreamDefaultStatusTest: Replaced version-derived expected stream with osImageStreamSetPredicate() that accepts any recognized stream (rhel-9 or rhel-10). The test still validates the controller populated the field from Machine NodeInfo.OSImage — it just doesn't predict which RHEL generation the payload ships.

  2. NodePoolOSImageStreamExplicitDefaultNoRolloutTest: Instead of predicting the default stream, polls for status.osImageStream to be set (via EventuallyObject + osImageStreamSetPredicate()), then reads the actual value from status to use for the no-rollout patch. This is both payload-agnostic and resilient to controller timing.

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

4 similar comments
@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@openshift-ci

openshift-ci Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

@bryan-cox: 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-kubevirt-aws-ovn-reduced cc60bc4 link true /test e2e-kubevirt-aws-ovn-reduced

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.

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aks

e2e-aws

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

11 similar comments
@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@bryan-cox

Copy link
Copy Markdown
Member Author

/test e2e-kubevirt-aws-ovn-reduced

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

2 similar comments
@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aks

e2e-aws

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

3 similar comments
@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aws

e2e-aks

@cwbotbot

Copy link
Copy Markdown

Test Results

e2e-aks

e2e-aws

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. area/testing Indicates the PR includes changes for e2e testing jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants