This bug was fixed in the package systemd - 229-4ubuntu11
---------------
systemd (229-4ubuntu11) xenial; urgency=medium
* 73-usb-net-by-mac.rules: Split kernel command line import line.
Reportedly this makes the rule actually work on some platforms. Thanks
Alp Toker! (LP: #1593379)
* fsckd: Do not exit on idle timeout if there are still clients connected
(Closes: #788050, LP: #1547844)
* libnss-*.prerm: Remove possible [key=value] options from NSS modules as
well. (LP: #1625584)
* Backport networkd 231. Compared to 229 this has a lot of fixes, some of
which we need for good netplan support. Backporting them individually
would be a lot more work and a lot less robust, and we did not use/support
networkd in 16.04 so far. Drop the other network related patches as they
are included in this backport now. (LP: #1627641)
* debian/tests/networkd: Re-enable the the DHCPv6 tests. The DHCPv6
behaviour is fixed with the above backport now.
* pid1: process zero-length notification messages again. Just remove the
assertion, the "n" value was not used anyway. This fixes a local DoS due
to unprocessed/unclosed fds which got introduced by the previous fix.
(LP: #1628687)
* pid1: Robustify manager_dispatch_notify_fd(). If
manager_dispatch_notify_fd() fails and returns an error then the handling
of service notifications will be disabled entirely leading to a
compromised system. (side issue of LP: #1628687)
-- Martin Pitt <martin.p...@ubuntu.com> Tue, 04 Oct 2016 21:43:04
+0200
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: nplan (Ubuntu Xenial)
Status: Fix Committed => 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/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 Released
Status in nplan source package in Xenial:
Fix Released
Status in systemd source package in Xenial:
Fix Released
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 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
