Bug 479524

Summary: system-config-network exception when editing virtual bridge
Product: [Fedora] Fedora Reporter: Stefan Zintgraf <s.zintgraf>
Component: system-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: dwmw2, harald, jmoskovc, lex.lists
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 07:33:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 516996    
Attachments:
Description Flags
Crashdump of the system-config-network tool. none

Description Stefan Zintgraf 2009-01-10 17:22:11 UTC 
My goal is to set up a bridged network with KVM and a Windows guest.
I am using Kernel 2.6.28 with kvm-82 based on Fedora Core 10 distribution.
I went through the tutorial in http://www.linux-kvm.com/content/tip-how-get-maximum-network-performance-using-paravirtual-drivers-and-bridged-networking.
I didn't use openvpn but tunctl instead to create the tap0 device.

The content of ifcfg-virbr1 file is as follows:
ONBOOT=yes
USERCTL=yes
NM_CONTROLLED=yes
TYPE=Bridge
DEVICE=virbr1
BOOTPROTO=dhcp

After creating the bridge device virbr1 i can see this device in the system-config-network tool. But when pressing 'edit' an exception occurs.

Version-Release number of selected component (if applicable):
system-config-network version 1.5.93
Comment 1 Stefan Zintgraf 2009-01-10 17:24:42 UTC 
Created attachment 328631 [details]
Crashdump of the system-config-network tool.
Comment 2 Bug Zapper 2009-11-18 10:42:56 UTC 
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Bug Zapper 2009-12-18 07:33:57 UTC 
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.