[systemd-devel] eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists

Tue Jan 4 13:46:29 UTC 2022

Hi folks,

after the upgrade from Buster to Bullseye (including the migration from
sysv init to systemd) the network interface names were messed up on
several hosts. Apparently udev stumbles over a naming conflict:

# journalctl -b | egrep -i e1000e\|igb\|rename\|eth\enp\|eno
Jan 03 11:30:14 nasl002b.example.com kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Jan 03 11:30:14 nasl002b.example.com kernel: igb: Intel(R) Gigabit Ethernet Network Driver
Jan 03 11:30:14 nasl002b.example.com kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e: Intel(R) PRO/1000 Network Driver
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.0: added PHC on eth0
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.0: eth0: (PCIe:5.0Gb/s:Width x4) a0:36:9f:00:06:1c
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.0: eth0: PBA No: G15139-001
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.1: added PHC on eth1
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4) a0:36:9f:00:06:1d
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.1: eth1: PBA No: G15139-001
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2: added PHC on eth2
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2: Intel(R) Gigabit Ethernet Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2: eth2: (PCIe:5.0Gb/s:Width x4) a0:36:9f:00:06:1e
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2: eth2: PBA No: G15139-001
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3: added PHC on eth3
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3: Intel(R) Gigabit Ethernet Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3: eth3: (PCIe:5.0Gb/s:Width x4) a0:36:9f:00:06:1f
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3: eth3: PBA No: G15139-001
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.2 eth4: renamed from eth2
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:00:19.0 eth2: (PCI Express:2.5GT/s:Width x1) 00:1e:67:19:34:6d
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:00:19.0 eth2: Intel(R) PRO/1000 Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:00:19.0 eth2: MAC: 10, PHY: 11, PBA No: 0100FF-0FF
Jan 03 11:30:14 nasl002b.example.com kernel: igb 0000:02:00.3 eth5: renamed from eth3
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:05:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:05:00.0 0000:05:00.0 (uninitialized): registered PHC clock
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:05:00.0 eth3: (PCI Express:2.5GT/s:Width x1) 00:1e:67:19:34:6c
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:05:00.0 eth3: Intel(R) PRO/1000 Network Connection
Jan 03 11:30:14 nasl002b.example.com kernel: e1000e 0000:05:00.0 eth3: MAC: 3, PHY: 8, PBA No: 1000FF-0FF
Jan 03 11:30:15 nasl002b.example.com kernel: igb 0000:02:00.1 enp2s0f1: renamed from eth1
Jan 03 11:30:15 nasl002b.example.com kernel: igb 0000:02:00.0 eno1: renamed from eth0
Jan 03 11:30:15 nasl002b.example.com kernel: e1000e 0000:05:00.0 enp5s0: renamed from eth3
Jan 03 11:30:15 nasl002b.example.com systemd-udevd[416]: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
Jan 03 11:30:20 nasl002b.example.com kernel: e1000e 0000:05:00.0 enp5s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Apparently udev stops renaming interfaces after the first conflict. eth4 and eth5
have kept their names, too, even thought there wouldn't be any further conflict:

# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether a0:36:9f:00:06:1c brd ff:ff:ff:ff:ff:ff
     altname enp2s0f0
3: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether a0:36:9f:00:06:1d brd ff:ff:ff:ff:ff:ff
4: eth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether a0:36:9f:00:06:1e brd ff:ff:ff:ff:ff:ff
     altname enp2s0f2
5: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether a0:36:9f:00:06:1f brd ff:ff:ff:ff:ff:ff
     altname enp2s0f3
6: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether 00:1e:67:19:34:6d brd ff:ff:ff:ff:ff:ff
     altname enp0s25
7: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
     link/ether 00:1e:67:19:34:6c brd ff:ff:ff:ff:ff:ff

systemd & udev is version 247.3-6, as included in Bullseye.

Every helpful comment is highly appreciated

Harri