** Description changed: + [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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712921 Title: enabling networkd appears to eat up entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
