Skip to content

Chrony

This page was the starting point for chrony, the chrony role of Ussuri. 2023.1 has no chrony role CODE: ansible/roles/ has no chrony directory, site.yml has no chrony play (its first service play is "Apply role common", site.yml:86-97), inventory/multinode has no chrony or chrony-server group, and kolla 2023.1 has no docker/chrony image. Kolla-Ansible no longer deploys a time service. Time sync is left to the host, and the only code that deals with it is a precheck (Before and after a run). The page keeps its sections so that links to it still resolve; each says what still applies.

Where to look

Operate

Impact and risk

  • What the tag executes (chrony): Tags §3 and Tags §3.1, rows chrony: nothing besides the always plays.
  • Risks: R2 and R25 no longer involve chrony: the common play is reached with -t common or an untagged run (R25 does not apply to 2023.1).

Dependencies

  • Dependencies: Component dependencies §2 (row "Chrony"), Component dependencies §5: no chrony container and no chrony.conf on any host, so the internal VIP and external_ntp_servers are no longer inputs of a compute host's configuration CODE (no reference to external_ntp_servers or chrony in ansible/ outside roles/prechecks/tasks/timesync_checks.yml).

Evidence

  • Fact sheet: fact sheet A §4 describes the Ussuri role.
  • Code for 2023.1: roles/prechecks/tasks/timesync_checks.yml:1-47 (host NTP daemon and clock checks), roles/prechecks/tasks/main.yml:7-9 (where they run), roles/prechecks/defaults/main.yml:6 (the switch).
  • Image side: Kolla images §5: no chrony image in kolla 2023.1.
  • Host side: ansible-collection-kolla (bootstrap-servers) neither installs nor configures an NTP daemon (no chrony or ntp in its roles/), and no longer removes the host chrony package (R14) CODE.

Before and after a run

  • kolla-ansible prechecks, on every host except those of the deployment group (roles/prechecks/tasks/main.yml:7-9) and only while prechecks_enable_host_ntp_checks is true (the default, roles/prechecks/defaults/main.yml:6; roles/prechecks/tasks/timesync_checks.yml:47) CODE:
    1. systemctl is-active chrony chronyd ntp ntpd systemd-timesyncd; fails with "No host NTP daemon is running" when the command's return code is not 0 (timesync_checks.yml:3-28);
    2. timedatectl status; fails when its output lacks synchronized: yes (timesync_checks.yml:30-46).
  • roles/prechecks/tasks/datetime_checks.yml:1-26 also fails when /etc/localtime is missing (all hosts) or /etc/timezone is missing (Debian family): both are bind-mounted into the containers (e.g. roles/iscsi/defaults/main.yml:42-43) CODE.
  • Set prechecks_enable_host_ntp_checks: false only when the host runs a daemon the check does not know, or one timedatectl does not recognise (the messages at timesync_checks.yml:21-26, :39-44).

Known limits and open points

  • The fact sheet items on the Ussuri role (fact sheet A §4.7, §4.8; fact sheet D §5.12): the VIP as internal time source, ip_nonlocal_bind on the chrony servers, the public pool default, a chrony restart stepping the clock. None of them applies to 2023.1: there is no chrony container, configuration or VIP time source to restart or reconfigure.
  • NOT AVAILABLE Which time source the hosts use, and how the operator configures it: the host NTP daemon is outside the Kolla-Ansible code. The precheck only proves that one of five daemons is active and that timedatectl reports a synchronised clock at precheck time; no deploy or reconfigure task checks it again.
  • NOT AVAILABLE What happens to a chrony container left on a host from an earlier release: no 2023.1 task stops, removes or checks it (no chrony reference in ansible/ outside the precheck that looks at host services).
  • R14: a bootstrap-servers re-run on a live host still removes host packages (open-iscsi, libvirt*, …), but chrony is no longer among them (ansible-collection-kolla roles/packages/defaults/main.yml:24-33).
  • Known bugs and limitations, Open questions and Findings have no entry on chrony.

Service card

The rows of the card are explained in How to read a service card.