LXD unit gets stuck at state: allocating, required charm profile not yet applied to machine

[Adam Dyess]

using juju 3.4

Steps to produce
I bootstrapped a fresh controller on lxd 5.20
I added a single model to the controller
I deployed a charm from charmhub (not a local charm) that had a lxd-profile.yaml within it

The container may have started before the charm completed its download, so the lxd-profile from the charm wasn't necessarily applied before the container began.

We observed the machine state available, but the charm state was

allocating required charm profile "k8s" not yet applied to machine

Looking at the controller mongo db, we saw that all the profiles expected to be deployed against the machine were
* the default profile
* the model profile
* the charm profile

Similarly, using lxd profile show, we saw all the profiles marked as "used by" that container.

Directed by juju, i stop and started the unit's agent on the unit (juju_stop_unit/juju_start_unit) but no change appeared on the unit's status.

We then restarted the container with lxd restart <id>

Still-- no change appeared on the unit status.