Bug 696659

Summary: Creating a bridge (br0) device on stock F15 system fails
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: netcfAssignee: David Lutterkort <lutter>
Status: CLOSED DEFERRED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bderzhavets, berrange, bodhi.zazen, crobinso, flammifer, hbrock, jforbes, jturner, laine, lutter, pcfe, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-20 15:21:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
/var/log/messages none

Description James Laska 2011-04-14 14:45:35 UTC 
Created attachment 492135 [details]
/var/log/messages

Description of problem:

After installing Fedora 15 (Beta), using virt-manager to create a bridge (br0) interface fails.  The dialogs present and accept my inputs, however it appears to fail while running 'ifup em1'

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install Fedora 15 Beta (or newer) - include @Virtualization
2. Login to desktop
3. Start virt-manager and connect to local libvirtd QEMU
4. Right click on local QEMU and select Details and choose 'Network Interfaces' tab
5. Attempt to create a bridged br0 device connected to em1
  
Actual results:

Error creating interface: 'Could not create interface: internal error failed to create (start) interface br0 (netcf: failed to execute external program - Running 'ifup em1' failed with exit code 3)'
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/createinterface.py", line 1137, in do_install
    self.interface.install(meter, create=activate)
  File "/usr/lib/python2.7/site-packages/virtinst/Interface.py", line 258, in install
    raise RuntimeError(errmsg)
RuntimeError: Could not create interface: internal error failed to create (start) interface br0 (netcf: failed to execute external program - Running 'ifup em1' failed with exit code 3)


Expected results:

The br0 device is created and activated as requested

Additional info:

 * Smolt hardware profile - http://www.smolts.org/client/show/pub_d487c327-3937-4a42-aaa3-072c2925b365
Comment 1 Boris Derzhavets 2011-04-23 12:48:27 UTC 
In meantime on F15 beta + (yum update) after failure :-

# cd /etc/sysconfig/network-scripts

and edit ifcfg-p37p1,ifcfg-br0 disabling NM

# cat ifcfg-p37p1 
DEVICE=p37p1
ONBOOT=yes
BRIDGE=br0
NM_CONTROLLED=no

# cat ifcfg-br0
DEVICE=br0
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.0.54
PREFIX=24
GATEWAY=192.168.0.1
DNS1=83.221.202.254
STP=off
DELAY=0
NM_CONTROLLED=no

# chkconfig network on
# service network start

[root@fedora15a ~]# ifconfig
br0       Link encap:Ethernet  HWaddr 90:E6:BA:2D:11:EB  
          inet addr:192.168.0.54  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::92e6:baff:fe2d:11eb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:88 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:13142 (12.8 KiB)  TX bytes:6967 (6.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:240 (240.0 b)  TX bytes:240 (240.0 b)

p37p1     Link encap:Ethernet  HWaddr 90:E6:BA:2D:11:EB  
          inet addr:192.168.0.54  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:112 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:22350 (21.8 KiB)  TX bytes:6969 (6.8 KiB)
          Interrupt:46 

virbr0    Link encap:Ethernet  HWaddr 06:DC:48:A0:60:60  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@fedora15a ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.90e6ba2d11eb	no		p37p1
virbr0		8000.000000000000	yes		

ifconfig seems a bit strange, but network is up.
Comment 2 Anton Chernyshov 2011-05-25 08:55:54 UTC 
May be it's because of this - https://bugzilla.redhat.com/show_bug.cgi?id=685053

After upgrade F14--> F15 I face with analog problem. In /etc/modprobe.d I have blacklist-ipv6.conf file, removing this file completely solve this problem.

Blacklist ipv6 kernel module make impossible to load bridge module, that needs to create network bridge.
Comment 3 Boris Derzhavets 2011-07-11 14:22:03 UTC 
I didn't find blacklist-ipv6.conf and attempted  to create bridge br0 via virt-manager. Procedure hangs , however under /etc/sysconconfig/network-scripts
it generated two files:

First

[root@fedora15 network-scripts]# cat ifcfg-p37p1
DEVICE="p37p1"
HWADDR=90:e6:ba:2d:11:eb
ONBOOT=yes
BRIDGE=br0
****************
I added
BOOTPROTO=dhcp
****************

Second

[root@fedora15 network-scripts]# cat ifcfg-br0
DEVICE=br0
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=none
IPADDR=192.168.0.167
GATEWAY=192.168.0.1
STP=on
DELAY=0
********************
I added
DNS1=ISP DNS SERVER
********************

I couldn't  bring up bridge without :-
# service network restart

Finally

[root@fedora15 network-scripts]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.90e6ba2d11eb	yes		p37p1
virbr0		8000.525400576642	yes		virbr0-nic

Scripts don't disable NM explicitly as it usually gets done.
But NM seems to be unable bring bridge up upon reboot
Comment 4 Cole Robinson 2011-07-11 17:22:54 UTC 
*** Bug 716983 has been marked as a duplicate of this bug. ***
Comment 5 Cole Robinson 2012-01-18 16:49:06 UTC 
Reassigning to netcf
Comment 6 Laine Stump 2012-01-20 15:21:02 UTC 
Problems of this nature were caused mainly NetworkManager not understanding bridge devices and ethernets attached to bridge devices, yet not being willing to give up control of the ethernet device - this problem was fixed in NetworkManager in time for F16 with one caveat - even in F16 if the ethernet config is changed and then ifup is immediately called for the ethernet, NM won't have noticed the change yet, and mess up the ifup (under the hood, /sbin/ifup calls nmcli).

Because of this "less than optimal" cooperation, the official line is that use of netcf to create bridges and bonds is only supported when NetworkManager is disabled. As such, I'm closing this bug. Feel free to re-open it if the operation fails when the NetworkManager service is disabled.

(In reply to comment #3)
> Scripts don't disable NM explicitly as it usually gets done.
> But NM seems to be unable bring bridge up upon reboot

NM doesn't understand bridges at all, so it can't bring up a bridge. NM in F16 will properly ignore a bridge, but that also means it won't be brought up. Upstream NM is in the process of integrating full bridge (and bond and vlan) support.