Allow server and pool sources to be overridden through a conf.d or sources.d configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chrony (Ubuntu) |
Fix Released
|
High
|
Ankush Pathak | ||
Bionic |
New
|
Undecided
|
Unassigned | ||
Focal |
New
|
Undecided
|
Unassigned | ||
Jammy |
New
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned | ||
Noble |
Triaged
|
High
|
Ankush Pathak |
Bug Description
[Impact]
Currently, the default chrony.conf configures a set of pools. If a user wishes to use only a specific server/server pool or not use the default servers at all, they will need to modify /etc/chrony/
There is an effort to move all configuration changes to their respective *.d directories. See: https:/
CPC test for modified ucf tracked chrony config file by invoking `sudo md5sum --quiet --check /var/lib/
Listing the cases where moving required chrony configuration changes to a *.d config is not possible
1. Azure: Azure needs all default pool entries in chrony.conf disabled. This is currently done by commenting out the pool entries in /etc/chrony/
2. Google: GCP images need to set a single server source entry. This is done indirectly through the ntp cloud-init module configuration. The ntp module replaces the default /etc/chrony/
[Workaround]
No known workaround
[Test Case]
* Upgrade a GCE Ubuntu instance from any supported release to Noble and the upgrade produces a chrony.conf ucf prompt.
* Run `sudo md5sum --quiet --check /var/lib/
[Where Problems Could Occur]
A case where debconf configuration that overrides default values prevents package installation scripts from configuring any chrony time sources.
This unlikely to happen without user intention in non-cloud environments.
Some cloud image builds are likely to do this on purpose to be able to configure cloud provider appropriate time sources.
CPC run tests on Ubuntu images for most cloud providers to ensure that chrony is configured with time sources.
-------
There is no request at this time to SRU the fix for this bug. Current intention is to land this in devel. The description follows the SRU template, just to better organize the bug summary.
-------
[Original Report]
Currently, the default chrony.conf configures a set of pools. Confirmed this on a focal and jammy instance on GCP. If one wishes to use only a specific server/server pool or not use a server at all they will need to modify /etc/chrony/
We are trying to move all configuration changes to their respective *.d directories. See: https:/
We test for modified chrony config file by invoking `sudo md5sum --quiet --check /var/lib/
Listing the cases that I know where we are not able to move chrony configuration changes to a *.d config
1. Azure: Azure needs all default pool entries in chrony.conf disabled. This is currently done by commenting out the pool entries in /etc/chrony/
2. Google: GCP images need to set a single server source entry. This is done indirectly through the ntp cloud-init module configuration. The ntp module replaces the default /etc/chrony/
This request perhaps can be extended to ensure that "negating" a configuration in the default /etc/chrony/
Related branches
- Andreas Hasenack: Approve
- git-ubuntu import: Pending requested
-
Diff: 253 lines (+115/-20)10 files modifieddebian/NEWS (+13/-0)
debian/changelog (+20/-0)
debian/chrony.conf (+1/-17)
debian/chrony.config (+10/-0)
debian/control (+1/-0)
debian/install (+1/-0)
debian/postinst (+26/-3)
debian/postrm (+14/-0)
debian/templates (+12/-0)
debian/ubuntu-ntp-pools.sources (+17/-0)
tags: | added: server-todo |
Changed in chrony (Ubuntu): | |
assignee: | nobody → Ankush Pathak (ankushpathak) |
importance: | Undecided → High |
description: | updated |
description: | updated |
tags: | removed: server-todo |
Status changed to 'Confirmed' because the bug affects multiple users.