Comment 18 for bug 2067474

To summarise:

1. Issue with a missing `/run/snap.maas` happened because chrony didn't start (it is not clear to me why)
The proper fix for this would be to create this path using snap install hook
https://code.launchpad.net/~troyanov/maas/+git/maas/+merge/466606

2. Agent should call `configure-agent` workflow that is sent towards `maas-temporal`
3. Regiond has `maas-temporal-worker` running aside that should provide all the required configurations back to the agent

So if agent is failing to start, then it might be either regiond & temporal-worker or something wrong with the temporal itself.

When you were installing snap did you get any errors? Who is the owner of maas database?