Bugzilla – Bug 1142800
systemd-networkd with kernel 5.2 don't up network interfaces
Last modified: 2019-07-29 07:22:27 UTC
The network is configured via systemd-networkd.
After update Tumbleweed to Kernel 5.2.1, I got a dead network.
At the same time, network and systemd-networkd are running and restarting them does not give anything.
The network is activated on only manually.
sudo ip link set enp3s0 up
If I updated remotely and restarted the computer, I would get a dead server.
Maybe openQA should add tests for systemd-netword?
SR https://build.opensuse.org/request/show/718032 fix network activation on startup.
Thanks for the report. As you already spotted, the fix has been submitted and should be part of the next update.
What about to prevent this in the future, and do QA tests for this?
Or does openQA test only what is by default, and those who use the systemd-netword do it at their own peril and risk?
Can you ask to upstream instead ?
It’s useless to ask Lenard "Notabug" Pottering upstream, there are at least a dozen of such bugs.
As it seems to me, the distribution kit in its QA should be engaged in checking the basic operability of the distribution kit.
I do not know how openQA is organized here, and how and who to offer?
Not all in a row to ask dimstar by email.
Moreover, I think that they even tested, but not with kernel 5.2, since they simply did not have it and could not do it.
Thomas, do you think this should worth to be check in openqa ?
IMO this should be checked by upstream so such issues are caught and fixed by them directly.
That said maybe it's already tested, it's just that kernel 5.2 has not yet been submitted and tested...
One more reason for upstream to test it I would say.
It looks like I missed your comment #7.
(In reply to Franck Bui from comment #8)
> Thomas, do you think this should worth to be check in openqa ?
> IMO this should be checked by upstream so such issues are caught and fixed
> by them directly.
This actually made openQA tests fail: https://bugzilla.opensuse.org/show_bug.cgi?id=1141597
(In reply to Dominik Heidler from comment #11)
> This actually made openQA tests fail:
Nope, again this one is a different issue.
*** Bug 1142901 has been marked as a duplicate of this bug. ***