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 1637901 - [NMCI][abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed by 6
Summary: [NMCI][abrt] [faf] NetworkManager: raise(): /usr/sbin/NetworkManager killed by 6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL: https://faf.lab.eng.brq.redhat.com/fa...
Whiteboard:
Depends On:
Blocks: 1654714
TreeView+ depends on / blocked
 
Reported: 2018-10-10 10:06 UTC by Vladimir Benes
Modified: 2019-08-06 13:16 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.18.0-0.3.20190408git43d9187c14.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:16:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2302 0 None None None 2019-08-06 13:16:45 UTC

Description Vladimir Benes 2018-10-10 10:06:00 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/ba9e175dda0a138004a9cdf67c8160f0a0da7222/
Comment 2 Beniamino Galvani 2018-11-26 16:56:30 UTC 
#0  in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/ra...
#1  in __GI_abort () at abort.c:90
#2  in g_assertion_message (domain=domain@entry=0x2aa0082f410 "NetworkMan...
#3  in g_assertion_message_expr (domain=domain@entry=0x2aa0082f410 "Netwo...
#4  in activate_stage5_ip4_config_result (self=0x2aa2f981d20) at src/devi...
#5  in activation_source_handle_cb (self=self@entry=0x2aa2f981d20, addr_f...
#6  in activation_source_handle_cb4 (user_data=user_data@entry=0x2aa2f981...
#7  in g_idle_dispatch (source=source@entry=0x2aa2f8f88b0, callback=0x2aa...
#8  in g_main_dispatch (context=0x2aa2f795a00) at gmain.c:3175
#9  in g_main_context_dispatch (context=context@entry=0x2aa2f795a00) at g...
#10 in g_main_context_iterate (context=0x2aa2f795a00, block=block@entry=1...
#11 in g_main_loop_run (loop=0x2aa2f795b40) at gmain.c:4097
#12 in main (argc=1, argv=0x3ffffd13bc8) at src/main.c:438

static void
activate_stage5_ip4_config_result (NMDevice *self)
{
    NMDevicePrivate *priv = NM_DEVICE_GET_PRIVATE (self);
    NMActRequest *req;
    const char *method;
    NMConnection *connection;
    int ip_ifindex;

    req = nm_device_get_act_request (self);
    g_assert (req); <=========================
Comment 3 Beniamino Galvani 2019-02-11 09:40:13 UTC 
Fixed by commit:

commit 260cded3d6a1dc8d8aa02f126908dc1667f163ed
Author: Beniamino Galvani <bgalvani>
Date:   Fri Jul 6 17:47:30 2018 +0200

    device: destroy pending acd-managers when the device disconnects
    
    We previously kept any acd-manager running if the device was
    disconnected. It was possible to trigger a crash by setting a long
    dad-timeout and interrupting the activation request:
    
      nmcli con add type ethernet ifname eth0 con-name eth0+ ip4 1.2.3.4/32
      nmcli con mod eth0+ ipv4.dad-timeout 10000
      nmcli -w 2 con up eth0+
      nmcli con down eth0+
    
    After this, the n-acd timer would fire after 10 seconds and try to
    disconnect an already disconnected device, throwing the assertion:
    
      NetworkManager:ERROR:src/devices/nm-device.c:9845:
      activate_stage5_ip4_config_result: assertion failed: (req)
    
    Fixes: 28f6e8b4d2ae554042027cb7af261289eb07e1e4

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/260cded3d6a1dc8d8aa02f126908dc1667f163ed
Comment 6 errata-xmlrpc 2019-08-06 13:16:24 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, 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-2019:2302
Note You need to log in before you can comment on or make changes to this bug.