bridge_ignore_without_connections.patch breaks NM created bridge at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
I've created a bridge with network-
First test-case:
Created a bridge with network-
Second test-case:
Created a bridge with network-
After compiling and testing different upstream versions, i could track the problem down to bridge_
I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) .
Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt.
Regards
Mathias Kresin
Changed in network-manager (Ubuntu): | |
status: | Incomplete → Confirmed |
That patch shouldn't be breaking the bridge though, since I'd expect it to match existing configs so as to implicitly exclude only bridges created outside NM, such as for lxc, libvirt, etc. It was definitely required in our testing.
I'd love to see the syslog message for this, and if possible with NM is debug mode. Could you attach the debugging logs for NetworkManager as you bring it up? It might help identifying the issue with this patch and fixing whatever might be wrong with it.
Thanks!