I built a d-i image against zesty-proposed, and verified that the installer showed predictable names for the onboard interfaces on a HiSilicon D05 server (see enahisi* in the attached screenshot). I used one of these interfaces for the install, and the system retained the configuration upon reboot.
** Attachment added: "d-i.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+attachment/4895416/+files/d-i.png ** Tags removed: verification-needed ** Tags added: verification-done-zesty ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Committed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
