Bug 1506552
| Summary: | [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed by 5 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | ||||
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.4 | CC: | atragler, bgalvani, fgiudici, lmiksik, lrintel, rkhan, sukulkar, thaller | ||||
| Target Milestone: | rc | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/774ec67a405f6ce3083d3a55d2876c2c5cc247b2/ | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | NetworkManager-1.10.2-6.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-04-10 13:31:31 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: | |||||||
| Attachments: |
|
||||||
|
Description
Vladimir Benes
2017-10-26 10:18:04 UTC
Fixed: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=33cb2f3723554b177803945d709d911cf6a3c77e The bug is present only in a package built from a master snapshot. reopening as I've seen it again Created attachment 1370049 [details]
[PATCH] settings: avoid assertion when deleting connections
(In reply to Beniamino Galvani from comment #5) > Created attachment 1370049 [details] > [PATCH] settings: avoid assertion when deleting connections I generally think it's a bug (misfeature) that we might re-add a connection -- and the need to clear the "removed" flag. Optimally, a connection instance doesn't get reused after being removed once. According to a9384452ed61ca3f1c6e1db175f499307da9c388, it's due to the NM_CONTROLLED=no instances. I think we shouldn't create such pseudo instances just to track the unmanaged-spec. IOW, we should drop create_unhandled_connection(). Can you add a "FIXME:" comment to nm_settings_connection_added() that this shouldn't really happen bug might? the patch lgtm for the moment. Added comment and applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=98ac0f404ed8103324b7d03cf04c24946f4543ff Backported to nm-1-10 as well. I can still see this, was it fixed? is it a duplicate? http://faf.lab.eng.brq.redhat.com/faf/problems/bthash/?bth=4872a3cccce41d5dbcd7180cf735487c9254c089 The stack trace at http://faf.lab.eng.brq.redhat.com/faf/problems/bthash/?bth=4872a3cccce41d5dbcd7180cf735487c9254c089 : 1 _g_log_abort 2 g_logv 3 g_log 4 g_closure_invoke 5 signal_emit_unlocked_R 6 g_signal_emit_valist 7 g_signal_emit 8 g_cancellable_cancel 9 _g_dbus_worker_close 10 g_dbus_connection_close 11 close_connection_in_idle 12 g_idle_dispatch 13 g_main_context_dispatch 14 g_main_context_iterate.isra.22 15 g_main_loop_run 16 main is different from the original one: 1 _g_log_abort 2 g_logv 3 g_log 4 g_type_check_instance_cast 5 nm_settings_connection_get_uuid 6 _nm_audit_manager_log_connection_op 7 delete_auth_cb 8 pk_auth_cb 9 auth_chain_finish 10 g_idle_dispatch 11 g_main_context_dispatch 12 g_main_context_iterate.isra.21 13 g_main_loop_run 14 main Can you file a new bug entry? 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-2018:0778 |