Bug 1535905

Summary:	gnome-control-center crashes when a team connection with configured link-watchers is present
Product:	Red Hat Enterprise Linux 7	Reporter:	Francesco Giudici <fgiudici>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lrintel>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.5	CC:	atragler, bgalvani, fgiudici, jreznik, lmiksik, lrintel, pgeorgie, rkhan, sukulkar, thaller, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.10.2-11.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 13:37:57 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:

Description Francesco Giudici 2018-01-18 09:01:32 UTC

The issue is due to a symbol clash between libjansson and libjson-glib: gnome-control-center loads libnm and libjson-glib. libnm loads libjansson. libjansson and libjson-glib have both the symbol "json_object_iter_next".

The clashing symbol is used both directly and indirectly:
* libnm uses "json_object_iter_next" directly through the macro "json_object_foreach" and "json_object_foreach_safe".
* libjansson uses the "json_object_iter_next" in many exposed APIs and links to libjson-glib symbol when called from gnome-control-center (via libnm).

The APIs that bring to the crash are called only when parsing a populated team.link-watchers property.

How reproducible:
* Create a team connection with a populated team.link-watchers property
* Try to start gnome-control-center

Comment 2 Pavlin Georgiev 2018-02-12 09:07:14 UTC

TEST SETUP
On machine qe-dell-ovs5-vm-1
under RHEL-7.5-20180201.2 x86_64 Workstation

Component version:
NetworkManager-1.10.2-11.el7

TEST PROCEDURE
* Add a new connection of type "team" and options "con-name team0 ifname nm-team autoconnect no ip4 1.2.3.4/24 connection.autoconnect-slaves yes"
* Add slave connection for master "nm-team" on device "eth1" named "team0.0"
* Bring "up" connection "team0"
* Set team.link-watchers to "ethtool" with parameters "delay-up=50", "delay-down=100"
* Bring "up" connection "team0"
* Start gnome-control-center
The bug does not appear.

RESULTS
Upgrading component: NetworkManager
to: 1.10.2-11.el7
has fixed the bug.

Comment 5 errata-xmlrpc 2018-04-10 13:37:57 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-2018:0778