← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1665088] Re: netplan bridge config doesn't support stp boolean

 

Verification done on xenial and yakkety with netplan 0.23~:

The parameters are being accepted by netplan parsing network v2 yaml;
and appropriately copied on to the resulting configuration for the
renderer. STP is not yet supported by systemd however, so further
testing could not be done.

** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu)
       Status: New => Fix Released

** Changed in: systemd (Ubuntu Zesty)
       Status: New => 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/1665088

Title:
  netplan bridge config doesn't support stp boolean

Status in netplan:
  Fix Released
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 Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  New
Status in nplan source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

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 config below; ensure behavior is as expected (STP value is set on the interface; adjust device names as appropriate). There should be no errors at applying the requested configuration.
  - Use the config below with the 'stp' key; the device should be brought up and include the default value set for the kernel.

  [Regression potential]
  STP default value should continue to be used for the bridge configured using netplan if STP is unset in configuration.

  ---

  networkd supports setting STP value in Bridge type netdevs, but
  netplan does not accept the key.

  root@ubuntu:/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
  root@ubuntu:/etc/netplan# lsb_release -rd
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04

  root@ubuntu:/etc/netplan# cat 52-bridge.yaml
  network:
      ethernets:
          eth0:
              addresses:
              - 10.11.12.13/24
              match:
                  macaddress: '52:54:00:12:34:00'
              set-name: foobar0
          eth1:
              match:
                  macaddress: '52:54:00:12:34:02'
              set-name: eth1
          eth2:
              match:
                  macaddress: '52:54:00:12:34:04'
              set-name: eth2
      bridges:
          br0:
              addresses:
              - 192.168.14.2/24
              interfaces:
              - eth1
              - eth2
              parameters:
                  ageing-time: 250
                  priority: 22
                  forward-delay: 1
                  hello-time: 1
                  max-age: 10
                  path-cost:
                      eth1: 50
                      eth2: 75
                  stp: true
      version: 2

  root@ubuntu:/etc/netplan# netplan generate
  Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: unknown key stp

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1665088/+subscriptions