Comment 23 for bug 1779621

Ok, could you please attach these files:

/lib/systemd/system/chrony.service
/lib/systemd/system/systemd-timesyncd.service

And if there are equivalent ones in /etc/systemd, those too. They could be overriding settings from the ones in /lib.

You might want to run this to find them:

find /lib/systemd/ -name 'chrony.service' -ls -o -name 'systemd-timesyncd.service' -ls

Same for /etc:

find /etc/systemd/ -name 'chrony.service' -ls -o -name 'systemd-timesyncd.service' -ls

On a working system, with both installed and where chrony is the only one starting up, I get:
root@bionic-chrony:~# find /lib/systemd/ -name 'chrony.service' -ls -o -name 'systemd-timesyncd.service' -ls
     1801 4 -rw-r--r-- 1 root root 1342 Apr 20 16:55 /lib/systemd/system/systemd-timesyncd.service
    63916 4 -rw-r--r-- 1 root root 567 May 23 14:21 /lib/systemd/system/chrony.service
root@bionic-chrony:~# find /etc/systemd/ -name 'chrony.service' -ls -o -name 'systemd-timesyncd.service' -ls
     1871 0 lrwxrwxrwx 1 root root 34 Jul 5 18:16 /etc/systemd/system/multi-user.target.wants/chrony.service -> /lib/systemd/system/chrony.service
      627 0 lrwxrwxrwx 1 root root 45 Jun 1 14:06 /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service