This isn't reproducible in yakkety, but it does reproduce locally in a
QEMU xenial instance (although a lot harder than on the infra, which is
why I didn't see it at first). It seems systemd 229's systemd-networkd-
wait-online has a bug that it does not actually wait for the interfaces
to be fully configured. When it exits, the status is
● 412: eth42
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-eth42.network
Type: ether
State: degraded (configured)
Driver: veth
HW Address: 0a:9b:04:93:f9:c0
MTU: 1500
Address: fe80::89b:4ff:fe93:f9c0
DNS: 2600:0000:0000:0000:0000:0000:0000:0001
i. e. the interface is still being set up. I would not like to work
around that in the tests, because if we are actually going to use
networkd on xenial the integration with network-online.target must work.
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => In Progress
--
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
