[Bug 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
Launchpad Bug Tracker
1945225 at bugs.launchpad.net
Mon Nov 21 09:31:40 UTC 2022
This bug was fixed in the package systemd - 245.4-4ubuntu3.19
---------------
systemd (245.4-4ubuntu3.19) focal; urgency=medium
[ dann frazier ]
* Add support for the v247 network naming scheme, but keep v245 as default
(LP: #1945225)
Author: dann frazier
Files:
- debian/patches/lp1945225/0001-udev-net_id-parse-_SUN-ACPI-index-as-a-signed-intege.patch
- debian/patches/lp1945225/0002-udev-net_id-don-t-generate-slot-based-names-if-multi.patch
- debian/patches/lp1945225/0003-net_id-fix-newly-added-naming-scheme-name.patch
- debian/patches/lp1945225/0004-Add-remaining-supported-schemes-as-options-for-defau.patch
- debian/rules
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f569231b5134a8e4901621ee5b2c33826184dae6
[ Dimitri John Ledkov ]
* test: fix test-execute autotest failure with kernel 5.15 (LP: #1975587)
File: debian/patches/test-make-test-execute-pass-on-Linux-5.15.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b3140ab5916269c020978ce678f06869a769f5c
-- Dimitri John Ledkov <dimitri.ledkov at canonical.com> Thu, 08 Sep 2022
10:58:15 +0100
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1945225
Title:
udev produces unpredictable net names when PCI device is a bridge
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Status in systemd source package in Impish:
Fix Released
Bug description:
[Impact]
udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13:
ubuntu at akis:~$ ls /sys/class/net
enp134s0f0 enp6s0 ens103 ens107 eth3 eth9
enp134s0f1 ens102 ens106 eth1 eth7 lo
For each ens* device, there is a sibling eth* device that maps to the
same slot because both devices are behind the same bridge.
Unpredictable names present well known problems, but I'll describe a
specific issue I'm having. We currently do automated network testing
that MAAS deploys a system and then configures 2 specific NICs on the
system. While MAAS does take care to always restore the names used
during commissioning (eth3 will always be the same NIC on every
deploy), these names can change each time the system is commissioned.
So today we need to go in and edit the NIC names manually in MAAS any
time the system is re-commissioned.
[Test Case]
Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names.
[Fix]
This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning.
[Regression Risk]
This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+subscriptions
More information about the foundations-bugs
mailing list