Comment 1 for bug 1855603

I am seeing a little bit different issue, but probably still the same cause(long application name)
I noticed this when rebooting the machine.
After the reboot, jujud unit could not start and got stuck in "agent initializing".
The following error was seen in /var/log/juju/machine-x.log

2020-07-08 10:23:01 ERROR juju.worker.dependency engine.go:663 "broker-tracker" manifold worker returned unexpected error: cannot create instance broker: creating LXD container manager: Get http://unix.socket/1.0: EOF
2020-07-08 10:23:03 ERROR juju.worker.dependency engine.go:663 "unit-agent-deployer" manifold worker returned unexpected error: remove /var/lib/juju/tools/unit-ubuntu-aaaaa-bbbbb-ccccc-ddddd-eeeee-fdcbf0ee8-0: no such file or directory

In my case, I'm seeing this when the application name is longer than 39 characters.
And here is the steps how I reproduced.

Using juju v2.7.7
1. bootstrap juju
juju bootstrap localhost
2. deploy an application with longer than 39 characters
juju deploy ubuntu ubuntu-aaaaa-bbbbb-ccccc-ddddd-eeeee-ff
3. after the deploy is completed, reboot the unit
juju run --unit ubuntu-aaaaa-bbbbb-ccccc-ddddd-eeeee-ff/0 -- sudo reboot

It looks like the systemd service name is created wrong.
$ systemctl list-unit-files | grep jujud
jujud-machine-0.service enabled
jujud-unit-ubuntu-aaa…bbbb-ccccc-ddddd-eeeee-fdcbf0ee8-0.service enabled