** Changed in: openssh (Ubuntu Zesty)
Status: New => Won't Fix
** Changed in: openssh (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: New => Invalid
** Changed in: systemd (Ubuntu Zesty)
Status: New => Invalid
** Changed in: systemd (Ubuntu Artful)
Status: Triaged => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Invalid
--
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/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:
Invalid
Status in nplan source package in Xenial:
Fix Committed
Status in openssh source package in Xenial:
Won't Fix
Status in systemd source package in Xenial:
Invalid
Status in nplan source package in Zesty:
Fix Committed
Status in openssh source package in Zesty:
Won't Fix
Status in systemd source package in Zesty:
Invalid
Status in nplan source package in Artful:
Fix Released
Status in openssh source package in Artful:
Fix Released
Status in systemd source package in Artful:
Invalid
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:
Invalid
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
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : [email protected]
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
