Comment 2 for bug 1938721

When charm ntp and maas snap are co-resident, two chronyd services start and listen. The winner of the race at boot time determines which clients can connect and which configuration is used to manage the local clock.

The ntp charm is typically the one we want to win the configuration battle, so charm-ntp should detect if ntp/chrony is installed via maas snap and then configure the maas chrony config file /var/snap/maas/current/etc/chrony/chrony.conf and manage the chrony service via maas snap.

The issue is not just in monitoring, but also accessibility/reachability for peers.