lxd profile written to wrong machine

[Heather Lanigan]

With the LXD provider, an LXD profile is written to the wrong machine when deploying inside an lxd container on an lxd juju machine.

$ juju add-model ovncentral
$ juju deploy cs:ovn-central -n 2 --to lxd,lxd
$ lxc profile list | grep ovncentral
| juju-ovncentral | | 5 | |
| juju-ovncentral-ovn-central-15 | | 0 |

$ juju ssh 0 -- sudo lxc profile list
+--------------------------------+---------------------+---------+
| NAME | DESCRIPTION | USED BY |
+--------------------------------+---------------------+---------+
| default | Default LXD profile | 1 |
+--------------------------------+---------------------+---------+
| juju-ovncentral-ovn-central-15 | | 1 |
+--------------------------------+---------------------+---------+
$ juju ssh 1 -- sudo lxc profile list
+--------------------------------+---------------------+---------+
| NAME | DESCRIPTION | USED BY |
+--------------------------------+---------------------+---------+
| default | Default LXD profile | 1 |
+--------------------------------+---------------------+---------+
| juju-ovncentral-ovn-central-15 | | 1 |
+--------------------------------+---------------------+---------+

When attempting to recreate 1957942 bootstrapped to localhost:
4/lxd/9 down pending focal cannot write lxd profiles: Error inserting "juju-seven-ovn-central-15" into database: The profile already exists

There was a lock and checks to prevent the above from happening. Not sure if it's related.