Comment 28 for bug 2067474

Thats good to know. Thank you for the provided information, we will try to figure out how that happened.

One thing that I still don't understand is why there were no socket and PID files for `chrony` and so far I don't see any errors related to `chrony`.

1. MAAS is crafting the following config:
(.ve) ubuntu@maas:~/maas$ sudo cat /var/snap/maas/x1/etc/chrony/maas.conf
# MAAS NTP configuration.
hwtimestamp *
pool ntp.ubuntu.com iburst
local stratum 8 orphan
allow
dumpdir /run/snap.maas/chrony
pidfile /run/snap.maas/chrony/chronyd.pid
bindcmdaddress /run/snap.maas/chrony/chronyd.sock

2. Chrony creates /run/snap.maas/chrony in a way similar to `mkdir -p`
3. Agent should recover if there is no dir, but eventually it will be created.

We will update the logic in the Agent to check if `/run/snap.maas` needs to be created