I just realized that the DHCPv6 failure that netplan's tests detect were already known in xenial's networkd tests; these tests got marked as "expected failure".
I started to backport individual networkd fixes, but this quickly became a frankensoftware which has never been tested in that form, and it would take prohibitively long to finish. Since 231, networkd development has slowed down considerably and it's by and large stable (judging by Debian bug reports a lot of people actually use it, and we did not get complaints since 231 any more). So in summary I think it is better to backport networkd 231 wholesale. In the running system it is completely independent of systemd and other tools (standalone binary), it has good test coverage, has been tried and tested in yakkety (unlike xenial when we did not yet use/support networkd), so IMHO the risk of this is lower than spending days on reengineering fixes on top of 229. The main noise of the backport is that this also requires backporting some common utility code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: In Progress Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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
