Skip to content

OCPBUGS-77499: aws/edge-zones: remove stale TEST_SKIPS for hairpinning test#75500

Open
wangke19 wants to merge 1 commit intoopenshift:mainfrom
wangke19:fix-OCPBUGS-77499-main
Open

OCPBUGS-77499: aws/edge-zones: remove stale TEST_SKIPS for hairpinning test#75500
wangke19 wants to merge 1 commit intoopenshift:mainfrom
wangke19:fix-OCPBUGS-77499-main

Conversation

@wangke19
Copy link
Contributor

Description

The TEST_SKIPS: internal should be reachable with hairpinning traffic workaround added in #75166 (referencing OCPBUGS-77166) is now causing CI failures. The test no longer exists in the filtered test suite for the aws/OVNKubernetes/edge-zones job configuration.

The openshift-e2e-test-commands.sh script validates that TEST_SKIPS matches at least one test before proceeding — when no match is found, the step exits with code 1 before any real tests run, blocking all PRs that trigger this job.

Changes

Remove the stale TEST_SKIPS workaround from:

  • ci-operator/step-registry/openshift/e2e/aws/edge-zones/openshift-e2e-aws-edge-zones-workflow.yaml
  • ci-operator/step-registry/openshift/e2e/aws/edge-zones/byo-vpc/openshift-e2e-aws-edge-zones-byo-vpc-workflow.yaml

Root Cause

From the failing job build #2027595494296915968:

time="2026-02-28T05:21:22Z" level=info msg="Discovered 7925 internal tests, 6399 external tests - 7402 total unique tests"
time="2026-02-28T05:21:22Z" level=info msg="Found 3534 filtered tests"
Skipping tests:
Error: no tests were found matching the TEST_SKIPS regex:
internal should be reachable with hairpinning traffic

The test internal should be reachable with hairpinning traffic is not present among the 3,534 filtered tests for the aws / OVNKubernetes / ipv4 / HighlyAvailable configuration. The hairpinning test was either renamed, removed, or filtered out by platform/network constraints.

Verification

The fix restores the behavior from before #75166: the test suite runs without any TEST_SKIPS filter, which is the correct state when the referenced bug (OCPBUGS-77166) is resolved or the test no longer exists.

Tracked in: https://issues.redhat.com/browse/OCPBUGS-77499


🤖 Generated with Claude Code via /jira:solve https://issues.redhat.com/browse/OCPBUGS-77499

…g test

The test "internal should be reachable with hairpinning traffic" no
longer exists in the filtered test suite for the aws/OVNKubernetes/
edge-zones job configuration. The openshift-e2e-test-commands.sh
script validates that TEST_SKIPS matches at least one test before
proceeding; when no match is found it exits with code 1, preventing
any real tests from running.

Remove the FIXME workaround that was added as a temporary skip for
OCPBUGS-77166. The referenced issue is either resolved or the test
has been renamed/removed from the suite, making this skip both
unnecessary and actively harmful to CI.

Applies to both the standard and BYO-VPC edge-zones workflows.
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 28, 2026
@openshift-ci-robot
Copy link
Contributor

@wangke19: This pull request references Jira Issue OCPBUGS-77499, which is invalid:

  • expected the bug to target the "4.22.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:

Description

The TEST_SKIPS: internal should be reachable with hairpinning traffic workaround added in #75166 (referencing OCPBUGS-77166) is now causing CI failures. The test no longer exists in the filtered test suite for the aws/OVNKubernetes/edge-zones job configuration.

The openshift-e2e-test-commands.sh script validates that TEST_SKIPS matches at least one test before proceeding — when no match is found, the step exits with code 1 before any real tests run, blocking all PRs that trigger this job.

Changes

Remove the stale TEST_SKIPS workaround from:

  • ci-operator/step-registry/openshift/e2e/aws/edge-zones/openshift-e2e-aws-edge-zones-workflow.yaml
  • ci-operator/step-registry/openshift/e2e/aws/edge-zones/byo-vpc/openshift-e2e-aws-edge-zones-byo-vpc-workflow.yaml

Root Cause

From the failing job build #2027595494296915968:

time="2026-02-28T05:21:22Z" level=info msg="Discovered 7925 internal tests, 6399 external tests - 7402 total unique tests"
time="2026-02-28T05:21:22Z" level=info msg="Found 3534 filtered tests"
Skipping tests:
Error: no tests were found matching the TEST_SKIPS regex:
internal should be reachable with hairpinning traffic

The test internal should be reachable with hairpinning traffic is not present among the 3,534 filtered tests for the aws / OVNKubernetes / ipv4 / HighlyAvailable configuration. The hairpinning test was either renamed, removed, or filtered out by platform/network constraints.

Verification

The fix restores the behavior from before #75166: the test suite runs without any TEST_SKIPS filter, which is the correct state when the referenced bug (OCPBUGS-77166) is resolved or the test no longer exists.

Tracked in: https://issues.redhat.com/browse/OCPBUGS-77499


🤖 Generated with Claude Code via /jira:solve https://issues.redhat.com/browse/OCPBUGS-77499

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 the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 28, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 28, 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
Copy link
Contributor

openshift-ci bot commented Feb 28, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@wangke19 wangke19 marked this pull request as ready for review February 28, 2026 09:01
@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 Feb 28, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@wangke19: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-5.0-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.23-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.22-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.21-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.20-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.19-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-origin-main-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-5.0-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.22-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.21-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.20-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.16-e2e-aws-ovn-edge-zones openshift/origin presubmit Registry content changed
pull-ci-openshift-installer-main-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.23-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.22-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.21-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.20-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.19-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed

A total of 77 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@mtulio
Copy link
Contributor

mtulio commented Feb 28, 2026

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@wangke19
Copy link
Contributor 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 Feb 28, 2026
@openshift-ci-robot
Copy link
Contributor

@wangke19: This pull request references Jira Issue OCPBUGS-77499, 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 (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, 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.

@wangke19
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-ovn-kubernetes-release-4.19-e2e-aws-ovn-edge-zones

@openshift-ci-robot
Copy link
Contributor

@wangke19: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 28, 2026

@wangke19: 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/rehearse/openshift/installer/release-4.23/e2e-aws-ovn-edge-zones 53687a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-4.23-e2e-aws-ovn-edge-zones
ci/rehearse/openshift/installer/release-4.21/e2e-aws-ovn-edge-zones 53687a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-4.21-e2e-aws-ovn-edge-zones
ci/rehearse/openshift/installer/release-5.0/e2e-aws-ovn-edge-zones 53687a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-edge-zones
ci/rehearse/openshift/installer/release-4.22/e2e-aws-ovn-edge-zones 53687a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-4.22-e2e-aws-ovn-edge-zones
ci/rehearse/openshift/installer/main/e2e-aws-ovn-edge-zones 53687a5 link unknown /pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-edge-zones

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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants