** Description changed: [Impact] Users of netplan may wish to specify a custom MTU value for a device. [Test case] - Run nplan integration tests on the release - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result) - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf - Validate that netplan generate && netplan apply works with any existing configuation. - Use the following config; ensure behavior is as expected (MTU value is set on the interface; adjust device name as appropriate): network: version: 2 ethernets: eno1: dhcp4: true mtu: 1280 - [Regression potential] - Any failure to work with existing configuration should be considered a regression. Any new failure of the test suite would be a regression. + Adding the 'mtu' setting on pre-existing valid configuration should not cause a failure to apply the configuration. Similarly, unchanged existing configurations should continue to behave as they previously did, with no changes in MTU values. --- - 1. root@z1:/etc/netplan# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 2. root@z1:/etc/netplan# apt-cache policy nplan nplan: Installed: 0.18 Candidate: 0.18 Version table: *** 0.18 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. netplan generate renders a config with MTU setting 4. root@z1:/etc/netplan# netplan generate Error in network definition //etc/netplan/simple.yaml line 4 column 6: unknown key mtu root@z1:/etc/netplan# cat simple.yaml network: version: 2 ethernets: eno1: dhcp4: true mtu: 1280 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nplan 0.18 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 28 16:47:13 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install)
** Also affects: nplan (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Yakkety) Importance: Undecided Status: New -- 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/1668693 Title: netplan fails to parse 'mtu' key Status in nplan package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in nplan source package in Yakkety: New Status in nplan source package in Zesty: New Bug description: [Impact] Users of netplan may wish to specify a custom MTU value for a device. [Test case] - Run nplan integration tests on the release - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result) - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf - Validate that netplan generate && netplan apply works with any existing configuation. - Use the following config; ensure behavior is as expected (MTU value is set on the interface; adjust device name as appropriate): network: version: 2 ethernets: eno1: dhcp4: true mtu: 1280 [Regression potential] Adding the 'mtu' setting on pre-existing valid configuration should not cause a failure to apply the configuration. Similarly, unchanged existing configurations should continue to behave as they previously did, with no changes in MTU values. --- 1. root@z1:/etc/netplan# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 2. root@z1:/etc/netplan# apt-cache policy nplan nplan: Installed: 0.18 Candidate: 0.18 Version table: *** 0.18 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. netplan generate renders a config with MTU setting 4. root@z1:/etc/netplan# netplan generate Error in network definition //etc/netplan/simple.yaml line 4 column 6: unknown key mtu root@z1:/etc/netplan# cat simple.yaml network: version: 2 ethernets: eno1: dhcp4: true mtu: 1280 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nplan 0.18 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 28 16:47:13 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1668693/+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