On Wed, May 20, 2015 at 8:05 PM, Michael Marineau <[email protected]> wrote: > I haven't retested HEAD yet but up through 219 it would report 'no-carrier > configuring' which seems bogus since it shouldn't be configuring an > interface in such a state
"no-carrier configuring" could easily happen as we would enslave a device and add routes/addresses even before the device gains a carrier. > and there is no .network config to apply to the > interface either. Now this is strange. A link should never be in "configuring" state unless we actually have a .network file to apply to it. > We have seen similar looking networkctl output for > physical interfaces too but since several different states get squashed into > 'configuring' I'm not sure if it is the same situation, it was just easier > to demo with a .netdev and bridge. Interestingly no other mechanism for > creating a bridge (ip or brctl) got it into the same state but I'm not sure > why. Not sure to be honest, I'll try to keep an eye on this, but as I said I have not been able to reproduce. Cheers, Tom _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
