Hello Dimitri, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done-zesty ** Tags added: verification-needed verification-needed-zesty -- 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/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 Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
