Bug 1221078

Summary: bond removal causes crash
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: control-centerAssignee: Rui Matos <rmatos>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: lmiksik, rmatos, tpelka, vbenes, vrutkovs
Target Milestone: betaKeywords: Regression
Target Release: 7.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 08:28:07 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 Flags
gdb backtrace fragment
none
valgrind log
none
valgrtind.log with G_DEBUG=fatal_warnings
none
full backtrace
none
new and much shorter backtrace none

Description Vladimir Benes 2015-05-13 09:23:44 UTC 
Description of problem:
removing bond in networking section causes crash. Sadly gdb crashed too when I was generating backtrace so attaching just a fragment. Nevertheless, reproducer is quite straightforward.  

Version-Release number of selected component (if applicable):
control-center-3.14.4-2.el7.x86_64

How reproducible:
50%

Steps to Reproduce:
1.open control-center->network
2.click +
3.select Bond
4.Save connection
5.select created bond in left tab
6.click -

Actual results:
crash

Expected results:
no crash

Additional info:
Comment 1 Bastien Nocera 2015-05-13 09:24:54 UTC 
I don't have hardware to reproduce a bonding setup. I'll need a backtrace of the crash in any case.
Comment 2 Vladimir Benes 2015-05-13 09:25:06 UTC 
Created attachment 1024971 [details]
gdb backtrace fragment
Comment 3 Vladimir Benes 2015-05-13 09:27:41 UTC 
(In reply to Bastien Nocera from comment #1)
> I don't have hardware to reproduce a bonding setup. I'll need a backtrace of
> the crash in any case.

you don't need it, just create profile and delete it. Simply follow reproducer steps.
Comment 4 Vladimir Benes 2015-05-13 09:29:38 UTC 
NetworkManager-1.0.0-14.git20150121.b4ea599c.el7.x86_64
Comment 5 Vladimir Benes 2015-05-13 11:30:41 UTC 
Created attachment 1025017 [details]
valgrind log
Comment 6 Vladimir Benes 2015-05-13 12:01:15 UTC 
Created attachment 1025035 [details]
valgrtind.log with G_DEBUG=fatal_warnings
Comment 7 Vladimir Benes 2015-05-13 12:03:08 UTC 
editor doesn't open at all for vlan, bridge, team, bond. Just ipsec vpn works.
Comment 8 Rui Matos 2015-05-25 15:08:09 UTC 
I was able to reproduce this once but not anymore. Can you still reproduce?

BTW, you can avoid that gdb crash if before you get the stack trace you set this in gdb's prompt:

set auto-load python-scripts off
Comment 9 Vladimir Benes 2015-05-25 18:33:47 UTC 
Created attachment 1029572 [details]
full backtrace
Comment 10 Vladimir Benes 2015-05-25 18:44:55 UTC 
Created attachment 1029595 [details]
new and much shorter backtrace
Comment 14 errata-xmlrpc 2015-11-19 08:28:07 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/RHBA-2015-2157.html