Bug 1376784

Summary:	segfault when Reapplying slave connection, without changes
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Haller <thaller>
Component:	NetworkManager	Assignee:	Beniamino Galvani <bgalvani>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	atragler, bgalvani, dcbw, extras-qa, fgiudici, lkundrak, lrintel, olichtne, ovasik, psimerda, rkhan, thaller, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.4.0-9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1376446	Environment:
Last Closed:	2016-11-03 19:30:30 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:
Bug Depends On:	1376446
Bug Blocks:

Description Thomas Haller 2016-09-16 12:06:45 UTC

+++ This bug was initially created as a clone of Bug #1376446 +++

Description of problem:
When I try to call Reapply of a bond slave ethernet connection NetworkManager crashes with a segfault (based on log in journalctl). This is using the interface exposed over D-Bus, using python.

Version-Release number of selected component (if applicable):
NetworkManager-1.4.0-4.fc26.x86_64

How reproducible:
always

Steps to Reproduce:
1. add bond connection
2. add slave ethernet connection
3. activate bond connection
4. activate slave connection
5. call Reapply on the device that the slave connection is applied on

Actual results:
Crash with segfault.

Expected results:
Nothing happens. Maybe an error of an invalid or "empty" operation.


Additional info:
python reproducer attached, example use:
./nm_reproducer.py ens9 52:54:00:38:c4:24



----

a crash, with a trivial fix.

Comment 4 Vladimir Benes 2016-09-19 21:10:52 UTC

working well in 1.4.0-9.el7

Comment 5 Beniamino Galvani 2016-09-20 07:49:06 UTC

*** Bug 1377589 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2016-11-03 19:30:30 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://rhn.redhat.com/errata/RHSA-2016-2581.html