Re: Predictable Network Interface Name Bug?

[Tim Safe <timsafeemail@xxxxxxxxx>]

Thanks for the reply! Here's the output:

$ udevadm test-builtin net_id /sys/class/net/ens8f0
Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Using default interface naming scheme 'v245'.
ID_NET_NAMING_SCHEME=v245
ID_NET_NAME_MAC=enx001b21708410
ID_OUI_FROM_DATABASE=Intel Corporate
ID_NET_NAME_PATH=enp5s0f0
ID_NET_NAME_SLOT=ens8f0
Unload module index
Unloaded link configuration context.

$ udevadm test-builtin net_id /sys/class/net/ens8f1
Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Using default interface naming scheme 'v245'.
ID_NET_NAMING_SCHEME=v245
ID_NET_NAME_MAC=enx001b21708411
ID_OUI_FROM_DATABASE=Intel Corporate
ID_NET_NAME_PATH=enp5s0f1
ID_NET_NAME_SLOT=ens8f1
Unload module index
Unloaded link configuration context.

$ udevadm test-builtin net_id /sys/class/net/eth2
Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Using default interface naming scheme 'v245'.
ID_NET_NAMING_SCHEME=v245
ID_NET_NAME_MAC=enx001b21708412
ID_OUI_FROM_DATABASE=Intel Corporate
ID_NET_NAME_PATH=enp6s0f0
ID_NET_NAME_SLOT=ens8f0
Unload module index
Unloaded link configuration context.

$ udevadm test-builtin net_id /sys/class/net/eth3
Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Using default interface naming scheme 'v245'.
ID_NET_NAMING_SCHEME=v245
ID_NET_NAME_MAC=enx001b21708413
ID_OUI_FROM_DATABASE=Intel Corporate
ID_NET_NAME_PATH=enp6s0f1
ID_NET_NAME_SLOT=ens8f1
Unload module index
Unloaded link configuration context.

On Thu, Dec 16, 2021 at 3:03 AM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote:

On Wed, Dec 15, 2021 at 09:37:41PM -0500, Tim Safe wrote:
> Hello-
>
> I have an Ubuntu Server 20.04 (systemd 245 (245.4-4ubuntu3.13)) box that I
> recently installed a Intel quad-port Gigabit ethernet adapter (E1G44ETBLK).
>
> It appears that the predictable interface naming is only renaming the first
> two interfaces (ens8f0, ens8f1) and the second two fail to be renamed
> (eth2, eth3).
>
> From the logs, I see the following messages:
>
> systemd-udevd[456]: eth2: Failed to rename network interface 5 from 'eth2'
> to 'ens8f0': File exists
> systemd-udevd[456]: eth2: Failed to process device, ignoring: File exists
> systemd-udevd[459]: ethtool: autonegotiation is unset or enabled, the speed
> and duplex are not writable.
> systemd-udevd[459]: eth3: Failed to rename network interface 6 from 'eth3'
> to 'ens8f1': File exists
> systemd-udevd[459]: eth3: Failed to process device, ignoring: File exists
>
> Taking a closer look at the PCI bus, I see:
>
> 05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
> Connection (rev 01)
> 05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
> Connection (rev 01)
> 06:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
> Connection (rev 01)
> 06:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
> Connection (rev 01)
>
> It looks like the adapter has two instances ending in '0' and two instances
> ending in '1'; they differ by the higher number ('05' vs '06') in the lspci
> output.
>
> Is this a bug? I'd expect to see the 3rd and 4th interfaces to be named
> ens8f2, ens8f3.

Can you provide the output from 'udevadm test-builtin net_id /sys/class/net/<iface>'
for each of the four interfaces?

Zbyszek