[Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

dann frazier dann.frazier at canonical.com
Tue Jul 11 15:29:50 UTC 2017


I upgraded systemd to 229-4ubuntu18 and removed /etc/udev/rules.d/70
-persistent-net.rules, and found that my onboard NICs are now using
predictable names:

ubuntu at d05-2:~$ ls /sys/class/net/
enahisic2i0  enahisic2i3   enP2p233s0f0  enP2p233s0f3  lo
enahisic2i1  enP10p17s0f0  enP2p233s0f1  enP5p113s0f0
enahisic2i2  enP10p17s0f1  enP2p233s0f2  enP5p113s0f1

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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/1686784

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  In Progress
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+subscriptions



More information about the foundations-bugs mailing list