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

[Martin Pitt]

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-
urandom/static/usr/local/bin/initialize-urandom.py has a very good
explanation of how the urandom pool is initialized. Based on that, this
unit drop-in speeds up urandom initialization by fake entropy:

# /etc/systemd/system/systemd-random-seed.service.d/fakeentropy.conf
[Service]
ExecStart=/usr/bin/perl -E 'open $$f, "/bin/bash" or die; open $$rnd, ">/dev/random" or die; for ($$i = 0; $$i < 10; ++$$i) {read $$f, $$d, 64; ioctl $$rnd, 0x40085203, pack("ii", 64*8, 64) . $$d}'


** Also affects: auto-package-testing
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnutls28 in Ubuntu.
https://bugs.launchpad.net/bugs/1622893

Title:
  NetworkManager takes very log to start, or times out, blocked on RNG

Status in Auto Package Testing:
  In Progress
Status in gnutls28 package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI     WWAN-HW  WWAN    
   running  1.2.2    connected  started  full          enabled     enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+subscriptions