Skip to content

OCPBUGS-86429: Unpin libreswan version for IPsec scaling fix - #1961

Open
anuragthehatter wants to merge 1 commit into
openshift:release-4.18from
anuragthehatter:unpin-libreswan-4.18
Open

OCPBUGS-86429: Unpin libreswan version for IPsec scaling fix#1961
anuragthehatter wants to merge 1 commit into
openshift:release-4.18from
anuragthehatter:unpin-libreswan-4.18

Conversation

@anuragthehatter

Copy link
Copy Markdown

Summary

Unpin libreswan from version 4.6 to enable consuming libreswan 5.x from the FDP repository, which resolves IPsec pluto segfaults at 75+ node scale in 4.18.z.

Background

At 75+ node IPsec mesh scale, libreswan 4.6 pluto crashes with a segfault in set_larval_v2_transition() during concurrent Child SA negotiation, causing permanent tunnel failures. Libreswan 5.x fixes this issue.

This reverts the pin added for OCPBUGS-43498, as libreswan 5.x resolves the scaling problem.

Related Changes

This is part of a coordinated set of PRs to unpin libreswan in 4.18.z:

References

🤖 Generated with Claude Code

This enables consuming libreswan 5.x from the FDP repository, which
fixes IPsec pluto segfaults at 75+ node scale in 4.18.z.

Reverts the pin added for OCPBUGS-43498, as libreswan 5.x resolves
the scaling issue with concurrent Child SA negotiation.

Bug: https://issues.redhat.com/browse/OCPBUGS-86429
Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66972299

Cherry-picked from: 9bb575a (openshift#1771)
Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
@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 Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@anuragthehatter: This pull request references Jira Issue OCPBUGS-86429, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-86429 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Summary

Unpin libreswan from version 4.6 to enable consuming libreswan 5.x from the FDP repository, which resolves IPsec pluto segfaults at 75+ node scale in 4.18.z.

Background

At 75+ node IPsec mesh scale, libreswan 4.6 pluto crashes with a segfault in set_larval_v2_transition() during concurrent Child SA negotiation, causing permanent tunnel failures. Libreswan 5.x fixes this issue.

This reverts the pin added for OCPBUGS-43498, as libreswan 5.x resolves the scaling problem.

Related Changes

This is part of a coordinated set of PRs to unpin libreswan in 4.18.z:

References

🤖 Generated with Claude 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 openshift-eng/jira-lifecycle-plugin repository.

@anuragthehatter

Copy link
Copy Markdown
Author

/assign @pperiyasamy for review

@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@anuragthehatter: GitHub didn't allow me to assign the following users: for, review.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @pperiyasamy for review

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
openshift-ci Bot requested review from jlebon and travier August 18, 2026 16:11
@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@anuragthehatter: 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/rhcos-9-build-test-qemu 632aa8e link true /test rhcos-9-build-test-qemu

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/invalid-bug Indicates that a referenced Jira bug is invalid 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