no-jira: aws: skip IPv6DualStack hostNetwork test in AWS dualstack techpreview presubmits#80172
no-jira: aws: skip IPv6DualStack hostNetwork test in AWS dualstack techpreview presubmits#80172tthvo wants to merge 1 commit into
Conversation
…review presubmits
The periodic jobs (e2e-aws-ovn-installer-dualstack-{ipv4,ipv6}-primary-techpreview)
already skip this test. Apply the same TEST_SKIPS to the installer presubmit
dualstack techpreview jobs for consistency.
TODO: Remove TEST_SKIPS once the upstream test is fixed and re-enable
running these tests. See kubernetes/kubernetes#121018
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@tthvo: This pull request explicitly references no jira issue. DetailsIn response to this:
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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (5)
WalkthroughFive OpenShift installer CI configuration files are updated to consistently skip a specific sig-network IPv6DualStack test case. The same ChangesIPv6 Dual-Stack HostNetwork Test Skip
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tthvo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-dualstack-ipv6-primary-techpreview |
|
@tthvo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-dualstack-ipv4-primary-techpreview |
|
@tthvo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/cc @patrickdillon |
|
@tthvo: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
The periodic jobs (
e2e-aws-ovn-installer-dualstack-{ipv4,ipv6}-primary-techpreview) already skip this test. Apply the sameTEST_SKIPSto the installer presubmit dualstack techpreview jobs for consistency.We should remove
TEST_SKIPSonce the upstream test is fixed and re-enable running these tests.See kubernetes/kubernetes#121018
Summary by CodeRabbit
This PR adds test skip configurations to the OpenShift installer's AWS OVN dual-stack techpreview presubmit jobs across multiple release branches (main, 4.22, 4.23, 5.0, and 5.1).
What's changing:
The PR adds a
TEST_SKIPSenvironment variable to both the IPv4-primary and IPv6-primary variants of thee2e-aws-ovn-dualstack-techpreviewjobs in each release branch. The skip targets this specific test case:Why:
This change aligns the presubmit job behavior with existing periodic jobs. The IPv6DualStack hostNetwork test is being skipped due to an upstream Kubernetes issue (kubernetes#121018). The TEST_SKIPS are temporary and should be removed once the upstream issue is resolved.
Impact: