[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#939328: marked as done (linux-image-4.19.0-5-amd64: buster and stretch-backports kernel causes interfaces rename back to ethX on HPe DL360g10)

Your message dated Tue, 29 Dec 2020 10:08:16 +0100
with message-id <20201229090816.GA2183@stormbind.net>
and subject line Closing #939328 - likely caused by a systemd misconfiguration
has caused the Debian Bug report #939328,
regarding linux-image-4.19.0-5-amd64: buster and stretch-backports kernel causes interfaces rename back to ethX on HPe DL360g10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
939328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939328
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 4.19.37-5+deb10u2
Severity: normal

Hi,
installing the latest update caused our NICs to be renamed from "enoX" back to "ethX". We first experienced
this issue on Debian/buster on HPe DL360g10 and now found the same issue with the latest upload of the same
kernel to stretch-backports.

We're now working around this issue by using
$ cat /etc/systemd/network/101-onboard-rd.link 
[Link]
NamePolicy=onboard kernel database slot path
MACAddressPolicy=none


That said on a system still running Debian/stretch with the old working kernel, without
the systemd workaround applied I've the following:

svenhoexter@docker-018:~$ uname -a
Linux docker-018 4.19.0-0.bpo.5-amd64 #1 SMP Debian 4.19.37-4~bpo9+1 (2019-06-19) x86_64 GNU/Linux

svenhoexter@docker-018:~$ udevadm test-builtin net_id /sys/class/net/eno5 2>/dev/null
ID_NET_NAME_ONBOARD=eno5
ID_NET_NAME_PATH=enp93s0f0

svenhoexter@docker-018:~$ SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/eno5
calling: test-builtin
=== trie on-disk ===
tool version:          232
file size:         8441068 bytes
header size             80 bytes
strings            1846908 bytes
nodes              6594080 bytes
Load module index
Found container virtualization none
timestamp of '/etc/systemd/network' changed
Skipping overridden file: /lib/systemd/network/99-default.link.
Parsed configuration file /etc/systemd/network/99-default.link
Created link configuration context.
ID_NET_DRIVER=i40e
No matching link configuration found.
Unload module index
Unloaded link configuration context.


On a system with the new kernel and the applied workaround we've:

svenhoexter@docker-019:~$ uname -a
Linux docker-018 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux

svenhoexter@docker-019:~$ udevadm test-builtin net_id /sys/class/net/eno5 2>/dev/null
ID_NET_NAMING_SCHEME=v240
ID_NET_NAME_ONBOARD=eno5
ID_NET_NAME_PATH=enp93s0f0

svenhoexter@docker-019:~$ SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/eno5
=== trie on-disk ===
tool version:          241
file size:         9492053 bytes
header size             80 bytes
strings            2069269 bytes
nodes              7422704 bytes
Load module index
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
timestamp of '/etc/systemd/network' changed
Skipping overridden file '/usr/lib/systemd/network/99-default.link'.
Parsed configuration file /etc/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/101-onboard-rd.link
Created link configuration context.
ID_NET_DRIVER=i40e
Config file /etc/systemd/network/101-onboard-rd.link applies to device eno5
link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
link_config: could not set ethtool features for eno5
Could not set offload features of eno5: Operation not permitted
eno5: Device has name_assign_type=4
Using default interface naming scheme 'v240'.
eno5: Policy *onboard* yields "eno5".
ID_NET_LINK_FILE=/etc/systemd/network/101-onboard-rd.link
ID_NET_NAME=eno5
Unload module index
Unloaded link configuration context.


Any hint on how to provide additional input is appreciated.

Sven

--- End Message ---
--- Begin Message --- 
Hi,
while reviewing parts of our infrastructure we noticed that we
did nasty things in /etc/systemd/network/99-default.link
which most likely caused this issue. Since the hosts which
we had this problem on are already gone, I can not be 100%
sure, but as far as we could replicate the issue we believe
that is it.

Closing the bug now, not a kernel issue.

Sven

--- End Message ---
Reply to: