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 1450075 - [NMCI] [abrt] [faf] NetworkManager: unknown function(): /usr/bin/nmcli killed by 11
Summary: [NMCI] [abrt] [faf] NetworkManager: unknown function(): /usr/bin/nmcli killed...
Keywords:
Status: CLOSED DUPLICATE of bug 1494065
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL: http://faf.lab.eng.brq.redhat.com/faf...
Whiteboard:
: 1436604 1447873 1457769 (view as bug list)
Depends On:
Blocks: 1470965
TreeView+ depends on / blocked
 
Reported: 2017-05-11 13:40 UTC by Vladimir Benes
Modified: 2017-11-07 13:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-07 13:53:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
output of `nmcli con up` (473.75 KB, text/plain)
2017-06-28 16:49 UTC, Thomas Haller 		no flags Details
View All

Description Vladimir Benes 2017-05-11 13:40:27 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/3af3e435cd5aa2b6297ef42d2154f67de6e9f934/
Comment 1 Thomas Haller 2017-05-11 15:39:14 UTC 
it is unclear to me how this crash could happen.

Reassigning to Lubomir for lack of a better idea.
Comment 2 Beniamino Galvani 2017-06-14 16:31:17 UTC 
*** Bug 1457769 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Haller 2017-06-15 19:22:52 UTC 
how about:

th/libnm-dbus-object-async-rh1450075

?

See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1457769#c2
https://bugzilla.redhat.com/show_bug.cgi?id=1457223
https://bugzilla.gnome.org/show_bug.cgi?id=783795#c1
Comment 4 Beniamino Galvani 2017-06-19 15:13:26 UTC 
(In reply to Thomas Haller from comment #3)
> how about:
> 
> th/libnm-dbus-object-async-rh1450075

Looks good to me.
Comment 5 Beniamino Galvani 2017-06-19 15:22:31 UTC 
*** Bug 1447873 has been marked as a duplicate of this bug. ***
Comment 6 Thomas Haller 2017-06-19 15:34:58 UTC 
merged upstream:

master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b1dcb3641780d5e587d802a1b8670a39b86877d

nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6fdf96d1d75c5a1f9b25f7cd3416603e844370be
Comment 7 Vladimir Benes 2017-06-28 09:55:35 UTC 
Moving to 7.5 as it's still not fixed even in 1.8-upstream/master branches
Comment 8 Thomas Haller 2017-06-28 16:49:22 UTC 
Created attachment 1292681 [details]
output of `nmcli con up`

the patches really break tests... strange.


Basically, restarting NM and issuing `nmcli conn up` right away hangs:

  systemctl restart NetworkManager
  G_DBUS_DEBUG=message LIBNM_GLIB_DEBUG=properties-changed G_MESSAGES_DEBUG=all nmcli conn up testeth0


The attached logfile has some printf debugging, but it's basically nm-1-8 (10ccdf4b814f631e39a551beb102860f65c5f25d).


note:

libnm-Message: >>>> recheck pending activations... 0x7f7298131cd0, no active connection on device 0x152f810

it's in recheck_pending_activations()
		if (!NM_IS_VPN_CONNECTION (candidate)) {
			device = devices->pdata[0];
			if (nm_device_get_active_connection (device) != candidate)
				continue;
		}

https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm/nm-manager.c?id=10ccdf4b814f631e39a551beb102860f65c5f25d#n840



The device's property never changes, although there are GDBus messages (grep for  0x152f810).
Comment 9 Thomas Haller 2017-06-29 08:06:01 UTC 
ok, reverted the patches from comment 6:


master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=95ff2b8e8a6a9b47da69b9cd6b406cc7e072b6e6

nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e96ee7fe5339e5a84fc6de722a3d309f5e9318f9


libnm seems to have still some issues. Need to fix them, but seems complicated.


Back to NEW.
Comment 10 Beniamino Galvani 2017-09-06 07:26:18 UTC 
*** Bug 1436604 has been marked as a duplicate of this bug. ***
Comment 11 Thomas Haller 2017-11-07 13:53:36 UTC 
The first attempt to fix it, caused other issues and was reverted (comment 9).

discussing with bgalvani, this looks like a duplicate of glib bug 1494065,
and should be fixed by backporting https://git.gnome.org/browse/glib/commit/?id=aeecd81dd13e4d8ef609149f82770ad06a8fccdb

(upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=788368 )


I am closing this a duplicate.

*** This bug has been marked as a duplicate of bug 1494065 ***
Note You need to log in before you can comment on or make changes to this bug.