starting lxd fails in a loop on slow machines

[Martin Pitt]

Yesterday I made another attempt at setting up LXD-based autopkgtesting on arm64 machines. I noticed that any "lxc" command hangs eternally, because lxd.service keeps flipping between "activating" and "deactivating", but never starts up properly.

It turns out that the lxd process was at 100% CPU, generating its server SSL certificate. But this took very long, and the default 90s startup timeout killed it before this was ready. Thus it got restarted, and goto 1.

lxd.service has

   ExecStartPost=/usr/bin/lxd waitready --timeout=600

Thus there needs to be a corresponding

  TimeoutStartSec=600

With that lxd.service gets enough time to generate its certs and all is well again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxd 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: i3
Date: Wed Apr 13 08:13:46 2016
EcryptfsInUse: Yes
SourcePackage: lxd
UpgradeStatus: No upgrade log present (probably fresh install)

[Stéphane Graber (stgraber)]

Doh, I could have sworn I had put the matching systemd timeout in there, will fix :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package lxd - 2.0.0-0ubuntu3

---------------
lxd (2.0.0-0ubuntu3) xenial; urgency=medium

  * Raise the systemd timeout to match the LXD startup timeout.
    This is needed on systems where TLS certificate generation takes a
    long time. (LP: #1569698)

 -- Stéphane Graber <email address hidden> Wed, 13 Apr 2016 12:43:54 -0400