[Bug 1142800] New: systemd-networkd with kernel 5.2 don't up network interfaces
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800 Bug ID: 1142800 Summary: systemd-networkd with kernel 5.2 don't up network interfaces Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: ilya@ilya.pp.ua QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- 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? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c1
--- Comment #1 from Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c2
--- Comment #2 from Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c3
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c4
--- Comment #4 from Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c5
--- Comment #5 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c6
--- Comment #6 from Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c7
--- Comment #7 from Илья Индиго
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c8
--- Comment #8 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c9
--- Comment #9 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c10
--- Comment #10 from Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c11
Dominik Heidler
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 https://openqa.opensuse.org/tests/990747 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c12
--- Comment #12 from Franck Bui
This actually made openQA tests fail: https://bugzilla.opensuse.org/show_bug.cgi?id=1141597 https://openqa.opensuse.org/tests/990747
Nope, again this one is a different issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800
http://bugzilla.opensuse.org/show_bug.cgi?id=1142800#c13
Franck Bui
participants (1)
-
bugzilla_noreply@novell.com