Bug 1450075
| Summary: | [NMCI] [abrt] [faf] NetworkManager: unknown function(): /usr/bin/nmcli killed by 11 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | ||||
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.4 | CC: | aloughla, atragler, bgalvani, fgiudici, lmiksik, lrintel, rkhan, sukulkar, thaller | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/3af3e435cd5aa2b6297ef42d2154f67de6e9f934/ | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-11-07 13:53:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1470965 | ||||||
| Attachments: |
|
||||||
|
Description
Vladimir Benes
2017-05-11 13:40:27 UTC
it is unclear to me how this crash could happen. Reassigning to Lubomir for lack of a better idea. *** Bug 1457769 has been marked as a duplicate of this bug. *** 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 (In reply to Thomas Haller from comment #3) > how about: > > th/libnm-dbus-object-async-rh1450075 Looks good to me. *** Bug 1447873 has been marked as a duplicate of this bug. *** merged upstream: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b1dcb3641780d5e587d802a1b8670a39b86877d nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6fdf96d1d75c5a1f9b25f7cd3416603e844370be Moving to 7.5 as it's still not fixed even in 1.8-upstream/master branches 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). 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. *** Bug 1436604 has been marked as a duplicate of this bug. *** 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 *** |