As another proposed workaround, I have found that editing /etc/init/rc-sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy /etc/init.d scripts until after the bridge interface comes up. I am not sure if this will have any other undesirable effects and clearly it would not work on a system without a bridge configured.
The best solution still has to be to migrate dhcp3-server to upstart but I hope this helps someone else out in the interim.
As another proposed workaround, I have found that editing /etc/init/ rc-sysinit. conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy /etc/init.d scripts until after the bridge interface comes up. I am not sure if this will have any other undesirable effects and clearly it would not work on a system without a bridge configured.
The best solution still has to be to migrate dhcp3-server to upstart but I hope this helps someone else out in the interim.