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

2017-10-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package systemd - 229-4ubuntu20

---
systemd (229-4ubuntu20) xenial; urgency=medium

  * resolved: recognize DNS names with more than one trailing dot as invalid
(LP: #160)
  * Ignore failures to set Nice priority on services in containers.
(LP: #1709536)
  * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
  * initramfs-tools: trigger udevadm add actions with subsystems first.
(LP: #1713536)
  * networkd: Add support to set STP value on a bridge. (LP: #1665088)
  * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings.
(LP: #1715131)
- Drop cherrypick of uint16 config parser, superseeded by above commit.
  * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135)
- networkd: add support to configure ARP, depedency of Primary/ActiveSlave.

 -- Dimitri John Ledkov   Tue, 05 Sep 2017 14:01:51
+0100

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

-- 
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/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 Released
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-10-03 Thread Francis Ginther 
** Tags added: id-596df0fafcee7c0b66ed241f

-- 
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/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 Released
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-10-02 Thread Dimitri John Ledkov 
229-4ubuntu19
netplan apply resulted in:
Oct 02 15:19:49 test-upgrade systemd[1]: Starting Network Service...
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:6] Unknown lvalue 'AgeingTimeSec' 
in section 'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:7] Unknown lvalue 'Priority' in 
section 'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: 
[/run/systemd/network/10-netplan-br0.netdev:11] Unknown lvalue 'STP' in section 
'Bridge'
Oct 02 15:19:49 test-upgrade systemd-networkd[1149]: br0: IPv6 enabled for 
interface: Success

229-4ubuntu20
netplan apply resulted in
Oct 02 15:21:35 test-upgrade systemd[1]: Starting Network Service...
Oct 02 15:21:35 test-upgrade systemd-networkd[3188]: br0: IPv6 enabled for 
interface: Success
Oct 02 15:21:35 test-upgrade systemd-networkd[3188]: br0: netdev ready


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

-- 
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/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 Released
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-09-19 Thread Brian Murray 
Hello Ryan, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu20
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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

-- 
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/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 Released
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-09-05 Thread Dimitri John Ledkov 
Staged for xenial at https://git.launchpad.net/~ubuntu-core-
dev/+git/systemd/commit/?id=5b2b8dff24492021fea8934d147361376968d4e1

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

-- 
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/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 Released
Status in systemd source package in Xenial:
  In Progress
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-07-21 Thread Dimitri John Ledkov 
** No longer affects: systemd (Ubuntu Yakkety)

-- 
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/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 Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-07-04 Thread Dimitri John Ledkov 
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3

-- 
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/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 Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Released
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

-- 
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

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

2017-06-27 Thread Launchpad Bug Tracker 
This bug was fixed in the package nplan - 0.23~16.10.1

---
nplan (0.23~16.10.1) yakkety; urgency=medium

  * Backport netplan 0.23 to 16.10. (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).

nplan (0.14) zesty; urgency=medium

  * tests/generate.py: Introduce macros for commonly expected networkd output
  * networkd: Use NetworkManager compatible DHCP route metrics (LP: #1639754)
  * doc/netplan.md: Fix wrong wifi reference in "br0" example
  * doc/netplan.md: Clarify introduction
  * tests/integration.py: Fix race condition with waiting for networkd

nplan (0.13) zesty; urgency=medium

  [ Jonathan Cave ]
  * Blacklist mwifiex_pcie from rebinds (work around LP: #1630285)

  [ Martin Pitt ]
  * Add support for nameservers (LP: #1626617)

 -- Mathieu Trudel-Lapierre   Tue, 06 Jun 2017
17:25:57 -0700

** Changed in: nplan (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
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/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 Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Released
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

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

2017-06-27 Thread Launchpad Bug Tracker 
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   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 Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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 Released
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:
   

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

2017-06-16 Thread Mathieu Trudel-Lapierre 
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 Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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

-- 
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

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

2017-06-16 Thread Mathieu Trudel-Lapierre 
Opened the task for systemd for xenial and yakkety. For STP controls to
work properly, STP support will have to be backported.

-- 
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/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

-- 
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