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.
Bug 1912423 - [NMCI] [abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed by 6
Summary: [NMCI] [abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed ...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Matej Berezny
URL: http://faf.lab.eng.brq.redhat.com/faf...
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-04 12:28 UTC by Vladimir Benes
Modified: 2021-11-10 06:46 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.32.4-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:28:55 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
there is a workaround deployed to avoid the crash, apply the attached patch to make it visible again (2.74 KB, application/mbox)
2021-01-04 20:23 UTC, Vladimir Benes
no flags Details
backtrace (32.50 KB, text/plain)
2021-07-13 12:48 UTC, Thomas Haller
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4361 0 None None None 2021-11-09 19:29:34 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 801 0 None opened vpn: change order of after/before scenario events in multiple_vpn_connections 2021-07-27 21:20:50 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 927 0 None opened [th/unrealized-vpn-crash] device: avoid crash setting VPN config during unrealize 2021-07-13 12:53:46 UTC

Description Vladimir Benes 2021-01-04 12:28:07 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/f99fe9fab63aaf2af4342514cc45db34832a6db4/

Comment 1 Vladimir Benes 2021-01-04 12:32:46 UTC
reproducible via multiple_vpn_connections

Comment 2 Vladimir Benes 2021-01-04 12:46:15 UTC
here it looks like it was first seen Mon Dec 21 21:57:01 2020

Comment 3 Vladimir Benes 2021-01-04 20:14:29 UTC
It is caused by our rework but the only thing we really have done is changing the order of cleaunp of libreswan BEFORE openvpn. If I change it to have cleanup of openvpn BEFORE libreswan there is no crash at all.

Comment 4 Vladimir Benes 2021-01-04 20:23:42 UTC
Created attachment 1744411 [details]
there is a workaround deployed to avoid the crash, apply the attached patch to make it visible again

Comment 5 Thomas Haller 2021-07-13 12:48:11 UTC
Created attachment 1801136 [details]

from FAF report "1:NetworkManager-1.29.6-27417.copr.2fa8ef9fb9.el8-ccpp-2020-12-21-20-59-07-473151"

Comment 6 Thomas Haller 2021-07-13 15:26:31 UTC
fixed and backported to nm-1-32.

Comment 11 errata-xmlrpc 2021-11-09 19:28:55 UTC
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 (Moderate: NetworkManager security, 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.


Note You need to log in before you can comment on or make changes to this bug.