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 1816067 - [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed by 5
Summary: [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL: https://faf.lab.eng.brq.redhat.com/fa...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-23 10:06 UTC by Vladimir Benes
Modified: 2020-11-04 01:50 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.25.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:49:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:50:03 UTC

Description Vladimir Benes 2020-03-23 10:06:27 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: https://faf.lab.eng.brq.redhat.com/faf/reports/bthash/3793271e5386234cfc7f2dcbc43435a00bca2bd3/

Comment 2 Thomas Haller 2020-03-23 12:38:49 UTC
should be fixed upstream:

master:  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/44fed3c3404efcb2a9db9e4a2ad6b87c3b9a44d8
nm-1-22: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/cdfb762880ff18c4581269bfaee7d4aa56a7ac50
nm-1-20: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/56c653eca53a8ece8d52c1b90a1cf15352a74b81
nm-1-18: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e905eb870ffed78040c804c80bb84be5f2d128fc

(thus, affecting all RHEL 8 and recent RHEL-7).

It is relatively severe, as it can lead to a crash, because we afterwards try to log a warning about the assertion failure (which leads to a NULL pointer dereference). On the other hand, it seems not not happen that easily, since it wasn't reported before.

Comment 5 Vladimir Benes 2020-05-20 12:04:19 UTC
FAF system has not seen it since     2020-03-22

Comment 8 errata-xmlrpc 2020-11-04 01:49:27 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 (NetworkManager 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/RHBA-2020:4499


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