tremplin: Better handling of failure modes

We assume that lxd, uevent socket and audit rule all exist or don't as a
set. This is leftover from when failing to create any of them killed
Tremplin, now that that's no longer the case it's possible for a failure
to result in e.g. the uevent socket to have been created but LXD to not
have been started causing failures when retrying to launch LXD.

BUG=chromium:1155437
TEST=start tremplin and fail to start LXD, then try again successfully

Change-Id: I1967e1dc7bd336815e742bd35a22c95650d02c75
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tremplin/+/2592287
Reviewed-by: Fergus Dall <sidereal@google.com>
Reviewed-by: David Munro <davidmunro@google.com>
Commit-Queue: David Munro <davidmunro@google.com>
Tested-by: David Munro <davidmunro@google.com>
4 files changed
tree: 2af7d82b798a03bbe12b7b1379394aadaaed263a
  1. .gitignore
  2. OWNERS
  3. README.md
  4. src/
README.md

Tremplin

Tremplin is the “springboard” daemon that runs in the Termina VM and exposes a gRPC interface for managing LXD containers.