Thank you Stéphane, in those log files I found the message:
device br0 already exists; can't create bridge with the same name
Failed to bring up br0.
In /etc/network/interfaces below the br0 stance I had just to remove
some lines:
pre-up brctl addbr br0
pre-up brctl addif br0 eth1
Please excuse the incomplete information; But I highly suspect it is
releated, and maybe some bells ring with the experts.
The week a system that I manage (xubuntu 12.04.1) failed to connect to
the net on reboot. The br0 bridge interface does not get fully
configured. There is nothing in syslog
The most relevant log files are in /var/log/upstart/network*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
bridge-utils/vlan udev hooks prevent execution of upstart
This bug was fixed in the package bridge-utils - 1.5-2ubuntu7
---
bridge-utils (1.5-2ubuntu7) precise-proposed; urgency=low
* Don't call ifup from udev hook, instead just create the bridge and let
upstart bring it up. Fixes hang at boot time. (LP: #1003656)
-- Stephane Graber
I have the same problem with quantal (image installed by MAAS)
I've just created a bridge br0 in the interfaces file and now the system does
not boot.
it seems br0 is not going up
if I do a brcrl addbr br0 everything works.
I have not the bonding one, but seems to be the same error.
The
I added a rule in udev to bring up the port directly with brctl addbr
br0 and now everything works.
But I don't know the cause.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/bridge-utils
/precise-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
bridge-utils/vlan udev hooks prevent
Gah, ignore my comment, perhaps the new version is working.
The issue I see now seems to be that on the last reboot the MAC address
of the bond has obtained the MAC of the other ethernet interface in the
bond rather than the MAC address of eth0 (which is the one hard wired in
my dhcpd config),
OK... if I force the MAC address of my bridge to be the one expected by
my dhcp server then 1.5-2ubuntu7 works.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan
Hello andrew, or anyone else affected,
Accepted bridge-utils into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/bridge-
utils/1.5-2ubuntu7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Rationale for not touching vlan is that it's never calling ifup and so
shouldn't be able to cause a similar deadlock situation as bridge-utils.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
I just spent a few minutes trying to figure out the ordering based on the
scripts for Andrew's system, it's basically:
- eth0 appears
- triggers udev
- triggers upstart
- triggers ifup eth0
- triggers bonding
- bond0 appears
- triggers udev
This bug was fixed in the package bridge-utils - 1.5-4ubuntu2
---
bridge-utils (1.5-4ubuntu2) quantal; urgency=low
* Revert last chance as udev doesn't accept that syntax.
* Set BRIDGE_HOTPLUG=yes as that's the behaviour we had in the past and
need for the event based
Also re-opening the bridge-utils task.
** Changed in: bridge-utils (Ubuntu Quantal)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
** Changed in: vlan (Ubuntu Quantal)
Status: Triaged = Invalid
** No longer affects: vlan (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Title:
Stéphane,
* Start vlan-network-interface in the background to avoid blocking the
rest of the udev events (most importantly the upstart one).
(LP: #1003656)
This doesn't appear to be a correct fix. I noticed here while working
on an unrelated boot issue that udev is now spitting
Hmm, that's odd, not sure why I didn't get these when I last tested the
change...
I'll put this one back on my todo for tomorrow to figure out how to
properly fix it or if I can't find a better way quickly, revert the
change.
--
You received this bug notification because you are a member of
** Summary changed:
- bond entries in /etc/network/interfaces fail without indent (when adding a
bond the bridge fails to acquire a dhcp address)
+ bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down
boot
--
You received this bug notification because you are a member
This bug was fixed in the package bridge-utils - 1.5-4ubuntu1
---
bridge-utils (1.5-4ubuntu1) quantal; urgency=low
* Start bridge-network-interface in the background to avoid blocking the
rest of the udev events (most importantly the upstart one).
(LP: #1003656)
--
A quick test on my test systems and on the reporter's system didn't show any
side effect, so I went ahead and pushed it to Ubuntu 12.10 in both the vlan and
bridge-utils packages.
I'll wait a few more weeks before pushing this to Ubuntu 12.04 so we can spot
any potential regression introduced
20 matches
Mail list logo
