Bug 1021947

Summary: segfault on creating bond device
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Pelka <tpelka>
Component: NetworkManagerAssignee: Jirka Klimes <jklimes>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.5CC: dcbw, jklimes, rkhan, tlavigne
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-0.8.1-66.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 21:51:17 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
nm log
none
more readable backtrace
none
[PATCH] ifcfg-rh: do not exit on invalid assertion (bond slave has IP setting) none

Description Tomas Pelka 2013-10-22 11:44:47 UTC
Created attachment 814948 [details]
nm log

Description of problem:


Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-63.el6

How reproducible:
100%

Steps to Reproduce:
1. Create new bond profile
2. add first slave
3. fill in correct HW address 

Actual results:
NM wrote the ifcfg-bond0_slave_1 but than segfaults

# cat ifcfg-bond0_slave_1 
TYPE=Ethernet
NAME="bond0 slave 1"
UUID=33f61793-363c-402d-b0b3-7c11a23631fd
ONBOOT=no
MASTER=4faf8a54-5124-46ce-9edf-0912cc40e214
HWADDR=52:54:00:69:00:C9


Expected results:
no segfault

Additional info:

Comment 1 Tomas Pelka 2013-10-22 12:30:29 UTC
Created attachment 814967 [details]
more readable backtrace

Comment 2 Jirka Klimes 2013-10-22 13:55:49 UTC
Created attachment 815013 [details]
[PATCH] ifcfg-rh: do not exit on invalid assertion (bond slave has IP setting)

Patch for RHEL-6.5 to fix crashing NM when saving a bond slave connection into ifcfg file.

Comment 8 errata-xmlrpc 2013-11-21 21:51:17 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.

http://rhn.redhat.com/errata/RHBA-2013-1670.html