Activity log for bug #1668693

Date Who What changed Old value New value Message
2017-02-28 16:53:12 Ryan Harper bug added bug
2017-02-28 22:00:26 Launchpad Janitor merge proposal linked https://code.launchpad.net/~raharper/netplan/+git/netplan/+merge/318545
2017-03-17 14:25:00 Mathieu Trudel-Lapierre nplan (Ubuntu): status New In Progress
2017-03-17 14:25:02 Mathieu Trudel-Lapierre nplan (Ubuntu): importance Undecided High
2017-03-17 14:25:05 Mathieu Trudel-Lapierre nplan (Ubuntu): assignee Mathieu Trudel-Lapierre (cyphermox)
2017-03-17 14:25:08 Mathieu Trudel-Lapierre nplan (Ubuntu): milestone ubuntu-17.03
2017-04-03 16:01:50 Mathieu Trudel-Lapierre nplan (Ubuntu): milestone ubuntu-17.03 ubuntu-17.05
2017-05-03 01:07:21 Launchpad Janitor nplan (Ubuntu): status In Progress Fix Released
2017-05-12 21:16:33 Mathieu Trudel-Lapierre description 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) [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. --- 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)
2017-05-18 21:59:29 Brian Murray nplan (Ubuntu Xenial): status New Fix Committed
2017-05-18 21:59:31 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-05-18 21:59:34 Brian Murray bug added subscriber SRU Verification
2017-05-18 21:59:39 Brian Murray tags amd64 apport-bug curtin uec-images zesty amd64 apport-bug curtin uec-images verification-needed zesty
2017-06-07 22:57:05 Mathieu Trudel-Lapierre 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] Any failure to work with existing configuration should be considered a regression. Any new failure of the test suite would be a regression. --- 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) [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)
2017-06-07 22:57:26 Mathieu Trudel-Lapierre nominated for series Ubuntu Zesty
2017-06-07 22:57:26 Mathieu Trudel-Lapierre bug task added nplan (Ubuntu Zesty)
2017-06-07 22:57:26 Mathieu Trudel-Lapierre nominated for series Ubuntu Yakkety
2017-06-07 22:57:26 Mathieu Trudel-Lapierre bug task added nplan (Ubuntu Yakkety)
2017-06-13 15:30:10 Brian Murray nplan (Ubuntu Zesty): status New Fix Committed
2017-06-13 18:31:56 Brian Murray nplan (Ubuntu Yakkety): status New Fix Committed
2017-06-16 18:56:17 Mathieu Trudel-Lapierre 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) [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)
2017-06-16 19:03:35 Mathieu Trudel-Lapierre tags amd64 apport-bug curtin uec-images verification-needed zesty amd64 apport-bug curtin uec-images verification-done-xenial verification-done-yakkety verification-done-zesty zesty
2017-06-27 14:45:29 Launchpad Janitor nplan (Ubuntu Xenial): status Fix Committed Fix Released
2017-06-27 14:46:00 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2017-06-27 15:46:26 Launchpad Janitor nplan (Ubuntu Yakkety): status Fix Committed Fix Released
2017-06-27 15:50:56 Launchpad Janitor nplan (Ubuntu Zesty): status Fix Committed Fix Released