If it is utilised, ignore-carrier=* breaks DHCP of the bridges.
Created attachment 881751 [details] NetworkManager bridge DHCP OK
Created attachment 881752 [details] NetworkManager bridge DHCP with ignore-carrier
So even with ignore-carrier, DHCP requires an actual network connection, so it will wait until the carrier is on until it starts DHCP. So NetworkManager is waiting for IP configurtion on the bridge until there is a carrier. But I do see in your logs: <info> (bridge0): link connected and at this point NetworkManager *should* be starting DHCP on bridge0 but it doesn't. What version of NetworkManager are you using, something from Fedora, or git master?
Nevermind, found the problem.
Created attachment 881815 [details] 0001-core-fix-bug-with-ignore-carrier-and-master-slave-de.patch Candidate patch
Pushed to git master after IRC acks.
Created attachment 881883 [details] NetworkManager bridge DHCP with ignore-carrier OK
Tested with git commit 42499b5. PASSED! Thanks Dan.
(In reply to Dan Williams from comment #3) > So even with ignore-carrier, DHCP requires an actual network connection, so > it will wait until the carrier is on until it starts DHCP. So > NetworkManager is waiting for IP configurtion on the bridge until there is a > carrier. > > But I do see in your logs: > > <info> (bridge0): link connected > > and at this point NetworkManager *should* be starting DHCP on bridge0 but it > doesn't. > > What version of NetworkManager are you using, something from Fedora, or git > master? Nothing fancy schmancy really, rebased & rebuild Rawhide's 'NetworkManager-0.9.9.1-4.git20140319.fc21.src.rpm' with a latest git commit tarballed at a certain time, e.g. 'NetworkManager-0.9.9.1.git20140402.42499b5.tar.bz2' , 'NetworkManager-0.9.9.1.git20140401.e9fdfa1.tar.bz2' , etc.