[Bug 1142901] New: systemd-networkd: Could not bring up interface: Invalid argument
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901 Bug ID: 1142901 Summary: systemd-networkd: Could not bring up interface: Invalid argument Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: tux93@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 811659 --> http://bugzilla.opensuse.org/attachment.cgi?id=811659&action=edit # SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-networkd After updating to Tumbleweed snapshot 20190723 systemd-networkd fails to bring up my network interfaces. <pre><code> # journalctl -u systemd-networkd -- Reboot -- Jul 25 19:30:22 tux93 systemd[1]: Starting Network Service... Jul 25 19:30:22 tux93 systemd-networkd[1669]: Enumeration completed Jul 25 19:30:22 tux93 systemd[1]: Started Network Service. Jul 25 19:30:22 tux93 systemd-networkd[1669]: enp3s0: Interface name change detected, enp3s0 has been renamed to eth0. Jul 25 19:30:22 tux93 systemd-networkd[1669]: eth0: Interface name change detected, eth0 has been renamed to enp3s0. Jul 25 19:30:22 tux93 systemd-networkd[1669]: eno1: Interface name change detected, eno1 has been renamed to eth0. Jul 25 19:30:22 tux93 systemd-networkd[1669]: eth0: Interface name change detected, eth0 has been renamed to eno1. Jul 25 19:30:22 tux93 systemd-networkd[1669]: enp3s0: Could not bring up interface: Invalid argument Jul 25 19:30:22 tux93 systemd-networkd[1669]: eno1: Could not bring up interface: Invalid argument Jul 25 19:30:23 tux93 systemd-networkd[1669]: virbr0-nic: Gained carrier Jul 25 19:30:23 tux93 systemd-networkd[1669]: virbr0-nic: Lost carrier Jul 25 19:30:23 tux93 systemd-networkd[1669]: virbr0-nic: Removing non-existent address: fe80::5054:ff:fed2:befb/64 (valid forever), ignoring </pre></code> <pre><code> # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190723" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190723" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190723" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" </pre></code> -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c1
Benoît Monin
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c2
Bernhard Held
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c5
Franck Bui
Same here. The issue depends on the kernel version. 5.1.x is OK, with 5.2 and later networkd doesn't bring up my bridge interface.
If the issue only appears with kernel 5.2, it sounds like boo#1142800 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c6
--- Comment #6 from Franck Bui
If the issue only appears with kernel 5.2, it sounds like boo#1142800
I already submitted a fix for this one to Base:System. You can give it a try here: https://build.opensuse.org/package/show/Base:System/systemd -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
Simon Schricker
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c7
--- Comment #7 from Bernhard Held
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c8
Dominik Heidler
Question is whether networkd is supposed to bring up the link layer vor virtual network interfaces. Looking at comment#2 it seems that this is rather a task of the kernel driver. Could someone from the kernel team please take a look?
For the record: It also happened one bare hardware (see my comment here: https://bugzilla.opensuse.org/show_bug.cgi?id=1141597#c9 ) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c9
Franck Bui
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c10
Dominique Leuenberger
Unfortunately it seems that kernel 5.2 has been released in TW before the networkd fix (available comment #6) was which lead to this bug.
Dominique do you confirm ?
If so can you please release a new version of systemd ASAP ?
Snapshot 0726 has kernel 5.2.2 and systemd 242 (your latest submission, sr#718032) The openQA tests fails nonetheless: https://openqa.opensuse.org/tests/993371#step/networkd_dhcp/31 (clearing needinfo for factory-auto in plus: the bot is shy and does not talk in bugs) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c11
--- Comment #11 from Marcel Kuehlhorn
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c12
--- Comment #12 from Franck Bui
The openQA tests fails nonetheless: https://openqa.opensuse.org/tests/993371#step/networkd_dhcp/31
It's 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=1142901
http://bugzilla.opensuse.org/show_bug.cgi?id=1142901#c13
Franck Bui
For me it is fixed with snapshot 20190726
It's then a duplicate of boo#1142800 *** This bug has been marked as a duplicate of bug 1142800 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com