[Bug 1712921] Re: enabling networkd appears to eat up entropy
Mathieu Trudel-Lapierre
mathieu.tl at gmail.com
Tue Nov 28 21:16:53 UTC 2017
nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the
code skipping the test_routes_v6 test in the NetworkManager case.
Therefore, it can't possibly pass SRU verification.
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1712921
Title:
enabling networkd appears to eat up entropy
Status in nplan package in Ubuntu:
Fix Released
Status in openssh package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in nplan source package in Xenial:
Fix Committed
Status in openssh source package in Xenial:
New
Status in systemd source package in Xenial:
New
Status in nplan source package in Zesty:
Fix Committed
Status in openssh source package in Zesty:
New
Status in systemd source package in Zesty:
New
Status in nplan source package in Artful:
In Progress
Status in openssh source package in Artful:
Fix Released
Status in systemd source package in Artful:
Triaged
Status in nplan source package in Bionic:
Fix Released
Status in openssh source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Triaged
Bug description:
[Impact]
Booting systems have a limited amount of entropy, especially in some of the cloud cases. We should avoid using it up unnecessarily.
[Test cases]
== netplan ==
1) Boot system with netplan config; using networkd renderer
2) Validate that it starts and does not cause undue delay.
2b) strace nplan at boottime (the netplan generator at /lib/systemd/system-generators/netplan) and validate it does not call get_random() / uuid_generate().
3) Validate that config with NetworkManager renderer generates UUIDs.
[Regression potential]
Netplan depends on UUID generation to create correct networkManager configuration for VLANs. This is a specific use-case that is typically not hit, but any failure to generate valid NetworkManager configuration would be a regression from this SRU.
---
enabling networkd appears to eat up entropy
as seen in openssh autopkgtest failing, when networkd is enabled by
default.
See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
triggers systemd/234-2ubuntu9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+subscriptions
More information about the foundations-bugs
mailing list