chrony config is wrong

[Cédric Jeanneret]

Hello,

Currently, we have these defaults for deployment/timesync/chrony-baremetal-ansible.yaml:

  NtpServer:
    default: ['0.pool.ntp.org', '1.pool.ntp.org', '2.pool.ntp.org', '3.pool.ntp.org']
  NtpPool:
    default: []

From the manpage, we can understand that "server" is for a host with a single IP, and "pool" is for a host with multiple IPs.

Since *.pool.ntp.org have multiple IPs for each names, it should use the "pool" entry instead of "server" entry in the configuration.

It might make things easier and cleaner for the retries.

[Alex Schultz (alex-schultz)]

This is done for backwards compatibility. It's intentional.

[Alex Schultz (alex-schultz)]

The history:

ntp only ever supported ntp servers, so we have --ntp-server in the cli, etc. These are not compatible with pool. Because everyone will have already defined NtpServer (and not pool), we can't configure pool by default. We only configure pool if explicitly defined. Not ideal, but this is a legacy carry over from NTP. Anyone upgrading would likely end up with invalid ntp configurations because the pool takes precedence of servers.