RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

'pluto' segfaults on establishment of tunnels between nodes in ipsec-enabled OCP 4.7 cluster.

Version-Release number of selected component (if applicable):
pluto-3.32-6

How reproducible:
Currently, we have no repeatable reproducer and it happens infrequently

Actual results:

kernel: pluto[7958]: segfault at 0 ip 00005562dc0fa6f6 sp 00007ffe9fc46a50 error 4 in pluto[5562dc067000+18c000]

Expected results:
No segmentation fault.

Additional info:
This issue has been raised upstream at https://github.com/libreswan/libreswan/issues/390

This is addressed in 4.x releases of libreswan, currently scheduled for RHEL 8.4

documentation of the bug can be seen at https://github.com/libreswan/libreswan/issues/390

I have implemented a workaround that restarts the container when a segmentation fault occurs. As I think this only happens at cluster installation time, this may be sufficient until the fix appears in 8.4 and that will then get pulled into the next version of OpenShift.

Verified SanityOnly.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libreswan bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1803