[Touch-packages] [Bug 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

Embarrassing workaround deployed to testing clouds: https://git.launchpad.net/~ubuntu-release/+git/autopkgtest- cloud/commit/?id=87dfd01d9 ** Changed in: auto-package-testing Importance: High => Undecided ** Changed in: auto-package-testing Status: In Progress => Fix Released -- You

[Touch-packages] [Bug 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

** Changed in: auto-package-testing Status: New => In Progress ** Changed in: auto-package-testing Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: auto-package-testing Importance: Undecided => Critical ** Changed in: auto-package-testing Importance: Critical =>

[Touch-packages] [Bug 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

I tried various workarounds for autopkgtest testbeds -- we *really* don't care for good random numbers there, and this causes awful delays in various tests. https://github.com/openstack-infra/project- config/blob/master/nodepool/elements/initialize-

[Touch-packages] [Bug 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

Downgrading libgnutls30 from 3.5.3 (current yakkety) to the previous upstream version 3.5.2 (https://launchpad.net/ubuntu/+source/gnutls28/3.5.2-2ubuntu4/) fixes this. So apparently libgnutls now does a blocking getrandom() on startup, which is rather unfriendly as you cannot use the library