The issue that you are running into is a duplicate of the bug above. MAAS uses cloud-init to configure NTP in the deployed machine. Cloud-init configures ntpd. However, due to bug #1597909, timesyncd is not being disabled.
That said, cloud-init will (in the near future) support the use of timesyncd instead. This can be tracked in [1]. Once that happens, MAAS will simply use the newer cloud-init to that purpose.
Hi Julen,
The issue that you are running into is a duplicate of the bug above. MAAS uses cloud-init to configure NTP in the deployed machine. Cloud-init configures ntpd. However, due to bug #1597909, timesyncd is not being disabled.
That said, cloud-init will (in the near future) support the use of timesyncd instead. This can be tracked in [1]. Once that happens, MAAS will simply use the newer cloud-init to that purpose.
[1]: https:/ /bugs.launchpad .net/cloud- init/+bug/ 1686485