| 2016-09-26 08:42:16 |
Martin Pitt |
bug |
|
|
added bug |
| 2016-09-26 08:42:28 |
Martin Pitt |
bug task added |
|
network-manager (Ubuntu) |
|
| 2016-09-26 08:42:41 |
Martin Pitt |
summary |
Provide nplan to xenial |
Backport netplan to xenial |
|
| 2016-09-26 08:42:47 |
Martin Pitt |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-09-26 08:42:47 |
Martin Pitt |
bug task added |
|
network-manager (Ubuntu Xenial) |
|
| 2016-09-26 08:42:47 |
Martin Pitt |
bug task added |
|
nplan (Ubuntu Xenial) |
|
| 2016-09-26 08:42:58 |
Martin Pitt |
bug |
|
|
added subscriber Simon Fels |
| 2016-09-26 08:43:03 |
Martin Pitt |
network-manager (Ubuntu): status |
New |
Fix Released |
|
| 2016-09-26 08:43:06 |
Martin Pitt |
nplan (Ubuntu): status |
New |
Fix Released |
|
| 2016-09-26 08:43:10 |
Martin Pitt |
network-manager (Ubuntu Xenial): status |
New |
Triaged |
|
| 2016-09-26 08:43:13 |
Martin Pitt |
network-manager (Ubuntu Xenial): assignee |
|
Martin Pitt (pitti) |
|
| 2016-09-26 08:43:16 |
Martin Pitt |
network-manager (Ubuntu Xenial): importance |
Undecided |
Wishlist |
|
| 2016-09-26 08:43:19 |
Martin Pitt |
nplan (Ubuntu Xenial): importance |
Undecided |
Wishlist |
|
| 2016-09-26 08:43:21 |
Martin Pitt |
nplan (Ubuntu Xenial): status |
New |
Triaged |
|
| 2016-09-26 08:43:23 |
Martin Pitt |
nplan (Ubuntu Xenial): assignee |
|
Martin Pitt (pitti) |
|
| 2016-09-26 09:28:40 |
Martin Pitt |
description |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
|
| 2016-09-26 09:31:44 |
Martin Pitt |
network-manager (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2016-09-26 10:21:20 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu) |
|
| 2016-09-26 10:21:29 |
Martin Pitt |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2016-09-26 10:22:14 |
Martin Pitt |
systemd (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-09-26 10:22:14 |
Martin Pitt |
systemd (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-09-26 10:22:14 |
Martin Pitt |
systemd (Ubuntu Xenial): assignee |
|
Martin Pitt (pitti) |
|
| 2016-09-26 10:31:06 |
Martin Pitt |
description |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4d4d305538
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
|
| 2016-09-26 10:32:30 |
Martin Pitt |
description |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4d4d305538
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4d4d305538
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
|
| 2016-09-26 16:02:49 |
Martin Pitt |
description |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4d4d305538
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
|
| 2016-09-26 20:11:57 |
Martin Pitt |
systemd (Ubuntu Xenial): importance |
High |
Wishlist |
|
| 2016-09-26 20:12:05 |
Martin Pitt |
systemd (Ubuntu Xenial): importance |
Wishlist |
Low |
|
| 2016-09-27 08:01:30 |
Andy Whitcroft |
systemd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-09-27 08:01:32 |
Andy Whitcroft |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-27 08:01:38 |
Andy Whitcroft |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-27 08:01:45 |
Andy Whitcroft |
tags |
|
verification-needed |
|
| 2016-09-27 09:30:04 |
Andy Whitcroft |
network-manager (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-09-27 10:41:53 |
Martin Pitt |
nplan (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2016-09-27 11:09:04 |
Mathew Hodson |
network-manager (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2016-09-27 11:09:58 |
Mathew Hodson |
nplan (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2016-09-27 11:10:02 |
Mathew Hodson |
systemd (Ubuntu): importance |
Undecided |
Low |
|
| 2016-09-27 12:46:52 |
Andy Whitcroft |
nplan (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-09-28 12:52:50 |
Martin Pitt |
systemd (Ubuntu Xenial): status |
Fix Committed |
In Progress |
|
| 2016-09-29 15:08:28 |
Martin Pitt |
description |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more.
netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager.
PATCHES:
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb
REGRESSION POTENTIAL:
netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades.
NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work.
systemd: This does change behavior of networkd quite a bit: RA is now being handled in userpsace instead of the kernel, there are some new virtual device types, LLDP support, etc., and there are no (known) backwards incompatibilities. The 229 version was known buggy with DHCPv6 (we disabled these two test cases), and judging by the feedback in Debian 231 is now reasonably stable. networkd is not being used by default or advertised in Ubuntu 16.04 (so far), so this will not affect the vast majority of installations. But while we have quite good test coverage, it cannot be ruled out that we break some custom setup that uses networkd.
TEST PLAN:
1. Run "NetworkManager --print-config" and save the output.
2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work.
3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1.
4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. |
|
| 2016-10-04 23:39:53 |
Chris Halse Rogers |
systemd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-10-06 05:20:24 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2016-10-12 08:23:22 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-10-12 08:23:18 |
Launchpad Janitor |
network-manager (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-12 08:37:09 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-12 08:37:49 |
Launchpad Janitor |
nplan (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
