Bridged networking start hangup at boot after kernel upgrade (2.6.28-13-server)

[Tobatus]

Binary package hint: bridge-utils

I had bridged networking for KVM with following configure:

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet static
 address 195.218.X.X
 netmask 255.255.X.X
 network 195.218.X.X
 broadcast 195.218.X.X
 gateway 195.218.X.X
 bridge_ports eth0
 bridge_fd 9
 bridge_hello 2
 bridge_maxage 12
 bridge_stp off

This worked fine before, but after latest (automatic) kernel upgrade, the server didn't come up from reboot. When I got to the console it was hanging at "Configuring network interfaces" message and needed to be interrupt with CTRL+ALT+DEL.

I changed network configuration just to use eth0 without bridge everything worked fine, expect the KVM guests.

ProblemType: Bug
Architecture: amd64
Dependencies:
 libgcc1 1:4.3.3-5ubuntu4
 gcc-4.3-base 4.3.3-5ubuntu4
 findutils 4.4.0-2ubuntu4
 libc6 2.9-4ubuntu6
DistroRelease: Ubuntu 9.04
Package: bridge-utils 1.4-5
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US
SourcePackage: bridge-utils
Uname: Linux 2.6.28-13-server x86_64

[Tobatus (toba-hukassa)]

I found work around and probably the reason. I noticed that iup -v -a hanged up at dhclient3-apparmor script, even that apparmor was disabled by chkconfig. After I removed the whole apparmor package the networking started to work again.

Why the script dhclient3-apparmor hanged, dunno.

[Jamie Strandboge (jdstrand)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. To help fix the bug, please follow the instructions found in https://wiki.ubuntu.com/DebuggingApparmor. This will greatly help us in tracking down your problem.

[Kees Cook (kees)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug '408773', so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.