This bug was fixed in the package systemd - 229-4ubuntu21.2
---------------
systemd (229-4ubuntu21.2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* udev: Mark ndb devices as inactive until connected. (LP: #696435)
* networkd: in dhcp, change UseMTU default to true, to accept DHCP provided
MTU by default.
(LP: #1717471)
* sysctl: apply parameters in-order, instead of randomly. (LP: #1718444)
* networkd: apply promote_secondaries, to make DHCP lease changes work.
(LP: #1721223)
* shutdown: sync filesystems, before going into a killing spree.
(LP: #1722481)
* sysctl: do not fail, when cannot apply sysctl changes due to read-only
sysfs in containers.
(LP: #1734409)
* networkd,wait-online: add RequiredForOnline to mark mandatory/optional
links for boot.
(LP: #1737570)
[ David Glasser ]
* journald: don't reduce BurstRateLimit on low disk space (LP: #1732803)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 21 Feb 2018 13:46:37
+0000
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1717471
Title:
networkd does not accept / set advertised mtu
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in nplan source package in Xenial:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in nplan source package in Zesty:
Fix Released
Bug description:
[Impact]
Hosts may require a specific MTU to be set as passed by DHCP options. We
should honor these settings to ensure proper communication of the host with the
rest of the network.
[Test case]
1) Run netplan on a system that should receive MTU settings from DHCP.
2) Validate that the MTU configuration provided by DHCP is applied to the
right interface.
[Regression Potential]
If DHCP settings specify an invalid MTU setting which is currently being
ignored and letting the systems communicate correctly with the network, then
these systems would regress.
---
<wgrant> Right, so as far as I can tell the neutron-api on lcy01 is
configured to advertise an instance interface MTU of 1400, though
that's lower than it has to be, and the new DHCP setup with networkd
just doesn't respect that DHCP option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
