This bug was fixed in the package systemd - 232-21ubuntu7
---------------
systemd (232-21ubuntu7) zesty; urgency=medium
* networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
* networkd: add support for ActiveSlave and PrimarySlave netdev options.
(LP: #1709135)
* Cherrypick upstream fix for a race between .mount and .automount units,
which currently may result in automounts hanging. (LP: #1709649)
* systemd.postinst: Fix-up version number check in the previous sru.
The version check in the postinst was too tight, thus the SRU fix failed
validation. (LP: #1710410)
systemd (232-21ubuntu6) zesty; urgency=medium
* link: Fix offload features initialization.
This fixes a regression introduced in v232 which caused TCP
segmentation offloads being disabled by default, resulting in
significant performance issues under certain conditions. (Closes: #864073)
(LP: #1703393)
* loginctl: Fix loginctl ignoring user given session IDs at command-line
(LP: #1682154)
* Disable fallback DNS servers.
This causes resolved to call-home to google, attempt to access network when
none is available, and spams logs. (LP: #1449001)
* initramfs-tools: trigger udevadm add actions with subsystems first.
This updates the initramfs-tools init-top udev script to trigger udevadm
actions with type specified. This mimicks the
systemd-udev-trigger.service. Without type specified only devices are
triggered, but triggering subsystems may also be required and should happen
before triggering the devices. This is the case for example on s390x with
zdev
generated udev rules. (LP: #1713536)
* Enable systemd-resolved by default. (LP: #1710410)
* core: fix systemd failing to serialize tasks correctly on daemon-reload.
(LP: #1702823)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 04 Oct 2017 14:22:02
+0100
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Committed => 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/1714933
Title:
Xenial: Please roll SRU with upstream fix for networkd to "accept
colons in network interface names"
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Zesty:
Fix Released
Status in systemd source package in Artful:
Fix Released
Bug description:
[Impact]
networkd cannot manage interface names with ':' in them. As used commonly, by
convention, by other tools.
[Fix]
Update networkd validation routines and test-suites to accept network
interface names with ':' in it.
[Testcase]
Create an inteface with ':' in its name and use it anywhere where systemd
validates ifname. E.g. Socket BindToDevice definition, nspawn network zone
info, Label= in [Address] section in networkd.
[Regression Potential]
This fix will change validation routines, and thus commands or settings that
were previously rejected or ignored will now take effect. Specifically Label=
settings in networkd may lead to networking conflicts. The justification for
this change is that networkd should really use the sensible ':' ifnames that
the user is requesting systemd to use.
[Original Bug Reprot]
PR: https://github.com/systemd/systemd/pull/5117
issue: https://github.com/systemd/systemd/issues/4057
Before the networkd from 231 was backported, it was possible to use
interface alias names that contained a colon, e.g. eth0:1. This is
commonly used to make legacy tools like "ifconfig" work, because they
*expect* a colon in the interface name.
Martin told me to file a bug for this.
Merging networkd from 231 lead to a regression where valid configs
were not accepted anymore after the backport. Please merge that fix
for the regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714933/+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
