Yeah, the traceback is unrelated. The bug is valid though, as even if the bridge is configured, if the l3-agent starts before OVS, the l3-agent will exit permanently, which is obviously bad.
I do think there's probably a decent argument to be made that the lack of an external bridge should probably not kill the entire service, so much as just prevent it from configuring gateways. I was trying to be very loud and upfront about the error, which makes sense if the process is started manually, but not if its a service that starts automatically and especially if it could start before OVS. There's also the point that if the l3-agent was only implementing routers with no gateway service, technically you wouldn't need an external gateway at all. That said, in several reboot on ubuntu at least, I saw this issue 1 out of 4 times, which is still enough that we need to treat this as a serious issue. The question is whether we should fix this in the code, or put the requirement on packagers. I tend to lean toward fixing it in the code, and instead checking and printing an error message and skipping router configuration in the router loop if no bridge is configured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052522 Title: L3 plugin exists / dies when external bridge isn't up To manage notifications about this bug go to: https://bugs.launchpad.net/quantum/+bug/1052522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
