group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1668693@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nplan - 0.23~16.04.1

---------------
nplan (0.23~16.04.1) xenial; urgency=medium

  * Backport netplan 0.23 to 16.04. (LP: #1688632)

nplan (0.23) artful; urgency=medium

  * Do not unbind brcmfmac, interface will be gone. (LP: #1696162)

nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
    (LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
    changes.

nplan (0.21) artful; urgency=medium

  [ Ryan Harper ]
  * Add support for setting MTU on a device. (LP: #1668693)

  [ Mathieu Trudel-Lapierre ]
  * Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
  * debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
    Both ship the same /usr/sbin/netplan. (LP: #1665842)

nplan (0.20) zesty; urgency=medium

  * tests/integration.py: increase timeout for integration tests (networkd and
    NetworkManager "wait-online" checks) to account for longer bring-up times
    when dealing with stacked virtual devices.

nplan (0.19) zesty; urgency=medium

  * Add support for unordered definition of network devices: you can now
    specify a virtual devices before their member devices. (LP: #1670495)
  * Allow setting up the STP state for a bridge. (LP: #1665088)
  * Document bond/bridge parameters support. (LP: #1664702)

nplan (0.18) zesty; urgency=medium

  * debian/tests/integration.py: in some cases 'iw reg get' may qualify the
    reg domain results with 'global'; we must not let that trip up tests when
    they are run on Ubuntu infrastructure vs. local tests.

nplan (0.17) zesty; urgency=medium

  * New release:
    - Add support for configuring bonds.
    - Add support for configuring bridges.

nplan (0.16) zesty; urgency=medium

  [ Martin Pitt ]
  * doc/example-config: Adjust "routes:" example.
    It does not make sense to make "routes:" a global thing, they should be
    tied to an interface so that the route is only set when the corresponding
    interface exists and is up, and the config is not split in two parts.
  * doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)

  [ Mathieu Trudel-Lapierre ]
  * Fix coverage for src/netplan to be 100%, and fail if coverage falls below
    that mark again.
  * Add support for specifying routes.

nplan (0.15) zesty; urgency=medium

  * tests/generate.py: Fix PEP-8 error (newly detected by -proposed
    pycodestyle).

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Tue, 06 Jun 2017
17:19:10 -0700

** Changed in: nplan (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/1668693

Title:
  netplan fails to parse 'mtu' key

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Yakkety:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed

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:
        match:
          macaddress: xx:xx:xx:xx:xx:xx
        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