Backport lxd-agent-loader into Bionic
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
New
|
Undecided
|
Unassigned | ||
Bug Description
The lxd-agent-loader package is present in Ubuntu Focal and onwards:
https:/
This package provides systemd units that detect when they are running inside a LXD VM and then start the lxd-agent (that is provided to the VM guest by way of a configuration drive that the units mount first).
The lxd-agent binary itself is *not* included in this package.
However because this package is not present in Bionic it is causing problems for various teams at Canonical who need to test their software on that operating system. It also causes issues for teams who are trying to diagnose & solve problems for ESM customers.
Because the lxd-agent process is not started inside the VM guests it is not then possible for LXD on the host to interact with the guest OS and so the following functions do not work:
* lxc exec
* lxc file [push|pull|mount]
* /dev/lxd inside the guest
* Status reporting of guest info in lxc info
With the recent move of LXD within the Canonical organisation there is a pending change to the serial device name that is exported from LXD to VM guests that these systemd units depend on:
https:/
So there will need to be an update to the lxd-agent-loader on the supported Ubuntu versions as well, but the LXD team will help with these changes.
