No way to configure timesyncd specifically
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
| cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Ubuntu (starting from Xenial), uses timesyncd by default as a NTP client.
When configuring NTP, instead of configuring Ubuntu's default NTP client, it installs and configures 'ntp' daemon. In Ubuntu Core, however, it configures 'timesyncd' (obviously) because Ubuntu Core doesn't support 'ntp'.
First, it would be nice to have consistency between both Ubuntu and Ubuntu Core and configure timesyncd (as it is the default anyway).
Second, lets imagine the use case scenario where a image is configured with NTP and you have an NTP snap or a snap that also needs to run NTP.
In Ubuntu core this works nicely because the OS' uses timesyncd as time source while the snap would provided NTP services from the snap itself to its client.
However, in Ubuntu this doesn't work nicely because 'ntp' is running in the host as an NTP client, however, the snap having NTP inside needs to provide NTP services, but it won't be able to provided that the host OS *also* has 'ntp' installed.
As such, it would be nice to either keep consistency (and configure timesyncd for both Ubuntu Core and Ubuntu), or have the ability to specifically configure 'timesyncd' instead of 'ntpd'.
| description: | updated |
| Changed in cloud-init: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in cloud-init (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| James Falcon (falcojr) wrote | #1 |
| Changed in cloud-init: | |
| status: | Confirmed → Fix Released |
| Changed in cloud-init (Ubuntu): | |
| status: | Confirmed → Fix Released |
| James Falcon (falcojr) wrote | #2 |
cc_ntp.py allows for configuring timesyncd and provides defaults for each distro. This was addressed in https:/