Skip to content

CNTRLPLANE-2999:Revert PR #30746: TLS 1.3 test causing instability in 4.22#30895

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
wangke19:revert-30746
Mar 18, 2026
Merged

CNTRLPLANE-2999:Revert PR #30746: TLS 1.3 test causing instability in 4.22#30895
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
wangke19:revert-30746

Conversation

@wangke19
Copy link
Contributor

Summary

This PR reverts #30746 which is causing test instability in 4.22 payloads.

Problem

Multiple test failures have been observed in periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade jobs after PR #30746 was merged:

Example failures:

As reported in #forum-testplatform Slack channel on 2026-03-17, the payload that had the test passing 10/10 before merge is now failing. The root cause appears to be the bundled library-go dependency bump in PR #30746.

Why Revert?

PR #30746 bundled two distinct changes:

  1. Test logic improvements: TLS 1.3 support, ECDSA handling, FIPS mode handling (valuable)
  2. Dependency update: library-go bump + personal fork for filepath-securejoin (problematic)

The dependency changes have introduced instability and need to be separated from the test logic improvements.

What Happens Next?

A replacement PR (#30894) has been prepared that:

Revert Details

This revert:

Related

/cc @team-technical-release

…faults-support"

This reverts commit 5c29d3af01fbee9cc0c6f748a8d2f1aac5c80a8e.

Reason for revert:
PR openshift#30746 is causing test instability in 4.22 payloads. Multiple test
failures have been observed in periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade
jobs as reported in #forum-testplatform Slack channel.

Example failures:
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-aws-ovn-upgrade-4.21-to-4.22-ci-openshift-release-analysis-aggregator/2033742335904321536
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade/2033742330044878848
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade/2033742330229428224
- https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade/2033742330355257344

The PR bundled test logic improvements with an unnecessary library-go
dependency bump, which has introduced instability. A follow-up PR (openshift#30894)
will reintroduce the test improvements without the dependency changes.

This revert is needed to:
1. Restore test stability in 4.22 CI
2. Separate test logic from dependency management concerns
3. Allow proper evaluation of the test improvements in isolation

Related:
- Original PR: openshift#30746
- Replacement PR: openshift#30894
- JIRA: OCPBUGS-76334
- Slack: #forum-testplatform discussion on 2026-03-17
@openshift-ci-robot
Copy link

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: automatic mode

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Mar 17, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d8353563-8e38-4c0d-8c2b-6f2a142e45dd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

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

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@stbenjam
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stbenjam, wangke19

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 Mar 17, 2026
@wangke19 wangke19 changed the title Revert PR #30746: TLS 1.3 test causing instability in 4.22 [NO=JIRA] Revert PR #30746: TLS 1.3 test causing instability in 4.22 Mar 17, 2026
@wangke19 wangke19 changed the title [NO=JIRA] Revert PR #30746: TLS 1.3 test causing instability in 4.22 [NO-JIRA] Revert PR #30746: TLS 1.3 test causing instability in 4.22 Mar 17, 2026
@stbenjam
Copy link
Member

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 17, 2026
@openshift-ci-robot
Copy link

@stbenjam: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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

/retest

@wangke19 wangke19 changed the title [NO-JIRA] Revert PR #30746: TLS 1.3 test causing instability in 4.22 CNTRLPLANE-2999:Revert PR #30746: TLS 1.3 test causing instability in 4.22 Mar 17, 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 Mar 17, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 17, 2026

@wangke19: This pull request references CNTRLPLANE-2999 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 bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

This PR reverts #30746 which is causing test instability in 4.22 payloads.

Problem

Multiple test failures have been observed in periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-upgrade jobs after PR #30746 was merged:

Example failures:

As reported in #forum-testplatform Slack channel on 2026-03-17, the payload that had the test passing 10/10 before merge is now failing. The root cause appears to be the bundled library-go dependency bump in PR #30746.

Why Revert?

PR #30746 bundled two distinct changes:

  1. Test logic improvements: TLS 1.3 support, ECDSA handling, FIPS mode handling (valuable)
  2. Dependency update: library-go bump + personal fork for filepath-securejoin (problematic)

The dependency changes have introduced instability and need to be separated from the test logic improvements.

What Happens Next?

A replacement PR (#30894) has been prepared that:

Revert Details

This revert:

Related

/cc @team-technical-release

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

/retest

@wangke19
Copy link
Contributor Author

/test e2e-metal-ipi-ovn-ipv6

1 similar comment
@wangke19
Copy link
Contributor Author

/test e2e-metal-ipi-ovn-ipv6

@stbenjam
Copy link
Member

/override ci/prow/e2e-metal-ipi-ovn-ipv6

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 18, 2026

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6

Details

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 18, 2026

@wangke19: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 12f8405 into openshift:main Mar 18, 2026
21 checks passed
@wangke19 wangke19 deleted the revert-30746 branch March 18, 2026 11:40
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. vendor-update Touching vendor dir or related files verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants