This bug was fixed in the package systemd - 233-6ubuntu2
---------------
systemd (233-6ubuntu2) artful; urgency=medium
[ Michael Biebl ]
* basic/journal-importer: Fix unaligned access in get_data_size()
(Closes: #862062)
[ Dimitri John Ledkov ]
* ubuntu: disable dnssec on any ubuntu releases (LP: #1690605)
* Cherrypick upstream patch for vio predictable interface names.
* Cherrypick upstream patch for platform predictable interface names.
(LP: #1686784)
[ Balint Reczey ]
* Skip starting systemd-remount-fs.service in containers
even when /etc/fstab is present.
This allows entering fully running state even when /etc/fstab
lists / to be mounted from a device which is not present in the
container. (LP: #1576341)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 17 May 2017 19:24:03
+0100
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
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:
New
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]
TBD - depends on the proposed solution.
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
