Chrony¶
This page was the starting point for chrony, the chrony role of Ussuri. 2024.1 has no chrony role, as 2023.1 had
none CODE: ansible/roles/ has no chrony directory (none of its 71 roles mentions chrony outside the prechecks),
site.yml has no chrony play (its first service play is "Apply role common", site.yml:88-103), inventory/multinode
has no chrony or chrony-server group, and kolla 2024.1 has no docker/chrony image. Kolla-Ansible does not deploy
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), unchanged since 2023.1. The page keeps its sections so that links to it still resolve;
each says what applies in 2024.1.
Where to look¶
Operate¶
- Scenario: none for chrony in 2024.1.
commonchanges are pushed with-t common(Applycommonchanges (fluentd, cron, kolla_toolbox) §3): the common play is taggedcommononly (site.yml:100-101). - Command: Apply
commonchanges (fluentd, cron, kolla_toolbox) §1.1:kolla-ansible -i multinode -t common reconfigure. - Command quick lookup by tag, row
-t chrony reconfigure: nochronyrole or play in 2024.1; only thealways-tagged plays run (fact gathering,site.yml:2andgather-facts.yml:26,:62; host grouping,site.yml:7-75) CODE. - Host time sync itself is checked by
kolla-ansible prechecks(tools/kolla-ansible:444-446setskolla_action=precheck; the prechecks play runs on the groupkolla_action_precheck,site.yml:77-86) CODE.
Impact and risk¶
- What the tag executes (
chrony): Tags §3 and Tags §3.1, rowschrony: nothing besides thealwaysplays. - Risks: R2 and R25 do not involve chrony: the
commonplay is reached with-t commonor an untagged run (site.yml:88-103).
Dependencies¶
- Dependencies: Component dependencies §2 (row "Chrony"),
Component dependencies §5: no chrony container and no
chrony.confon any host, so the internal VIP andexternal_ntp_serversare not inputs of a compute host's configuration CODE:ansible/has no reference toexternal_ntp_servers, and none tochronyoutsideroles/prechecks/tasks/timesync_checks.yml. The only other NTP setting is the per-rangentp_serverDHCP option of Ironic's dnsmasq (roles/ironic/templates/ironic-dnsmasq.conf.j2:13), which is handed to the bare-metal nodes Ironic provisions, not to the Kolla hosts.
Evidence¶
- Fact sheet: fact sheet A §4 describes the Ussuri role.
- Code for 2024.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:5-6(the switch). Still holds in 2024.1 CODE:timesync_checks.ymlanddatetime_checks.ymlare identical to their 2023.1 versions. - Image side: Kolla images §5: no chrony image in kolla 2024.1.
- Host side: ansible-collection-kolla 2024.1 (
bootstrap-servers) neither installs nor configures an NTP daemon (nochrony,ntportimesyncin itsroles/; its package lists areroles/packages/defaults/main.yml:10-34), and does not remove the hostchronypackage (R14) CODE.
Before and after a run¶
kolla-ansible prechecks, on every host except those of thedeploymentgroup (roles/prechecks/tasks/main.yml:7-9) and only whileprechecks_enable_host_ntp_checksis true (the default,roles/prechecks/defaults/main.yml:6;roles/prechecks/tasks/timesync_checks.yml:47) CODE: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);timedatectl status; fails when its output lackssynchronized: yes(timesync_checks.yml:30-46).
roles/prechecks/tasks/datetime_checks.yml:1-26also fails when/etc/localtimeis missing (all hosts) or/etc/timezoneis missing (Debian family): both are bind-mounted into the containers (e.g.roles/iscsi/defaults/main.yml:43-44) CODE. It is imported for every host the prechecks play runs on (roles/prechecks/tasks/main.yml:11), thedeploymentgroup included.- Set
prechecks_enable_host_ntp_checks: falseonly when the host runs a daemon the check does not know, or onetimedatectldoes not recognise (the messages attimesync_checks.yml:21-26,:39-44). - The prechecks play runs only when
kolla_actionisprecheck(site.yml:77-86):deploy,reconfigureandupgradedo not run these checks CODE.
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_bindon the chrony servers, the public pool default, a chrony restart stepping the clock. None of them applies to 2024.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
timedatectlreports a synchronised clock at precheck time; no deploy or reconfigure task checks it again. - NOT AVAILABLE What happens to a
chronycontainer left on a host from an earlier release: no 2024.1 task stops, removes or checks it (nochronyreference inansible/outside the precheck that looks at host services). - R14: a
bootstrap-serversre-run on a live host still removes host packages (open-iscsi,libvirt*, …), butchronyis not among them (ansible-collection-kollaroles/packages/defaults/main.yml:25-34, removed byroles/packages/tasks/main.yml:15-23) CODE. - 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.
Related¶
- Apply
commonchanges (fluentd, cron, kolla_toolbox) —-t common reconfigure, the command that pushescommonchanges (there is no-t chronyplay) - Common: fluentd, cron, kolla_toolbox — the
commonrole and its own play - HAProxy + Keepalived — the loadbalancer role; the VIP is not a time source
- Component dependencies §5 — the global inputs of a compute host
- Components — the other component pages