New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression: networkd-wait-online times out, interface never goes from "carrier" to "routable" #1645
Comments
I suppose the reason for that is that "State" used to be "routable (configured)" but now is "carrier (configured)", although the routes do look okay. |
Another observation: Our network test has four checks: (IPv4 or IPv6) x (hotplug or coldplug). Not all of them always fail, sometimes one or two actually succeed. So this smells like a race condition. |
Bisected to 84de38c5691 . That's quite a big one; @teg, do you see this as well? This doesn't say anything about changing status names, so I figure "status carrier" is the bug here, and wait-online timing out is merely telling that it never goes to "routable"? |
Things work again if I revert just this one hunk, i. e. I apply this patch:
I'm fairly sure that this isn't what @teg intended with 84de38c5691, but it goes back to a known-working state, so I'll apply that to my "trunk CI" branch for the time being to be able to run tests on trunk again. (This doesn't get released to anywhere but the daily PPA). |
Revert one hunk from commit 84de38c which caused links to stay in state "carrier (configured)" forever, instead of going to "routable (configured)". This most probably isn't what commit 84de38c intended to do, but it goes back to a known-working state. Fixes systemd#1645
I can still reproduce this at 84de38c, but not any more on current master. So I'm closing this. I ran a git bisect but that was inconclusive; this is a race condition and thus the automatic test doesn't catch this every time; also, they occasionally fail for other reasons. I might do it again tomorrow with manual testing, just to turn this from "magically fixed" to "aah, so that was it". |
I'm seeing this on a raspberry-pi2 with ArchLinux on Arm (ALArm) after I disabled IPv6 via kernel boot commandline; though, I'm not sure if the problem is directly related to that or a recent update.
Followed by the failed state line |
systemd-networkd[275]: eth0: Could not set route: Network is unreachable
|
Our "networkd" integration test got broken since the last few days in master. networkd itself seems to work fine:
Network is operational, I can ssh in and ping out etc. However:
Going to bisect now.
The text was updated successfully, but these errors were encountered: