+++ This bug was initially created as a clone of Bug #2042689 +++ Description of problem: Rebooting of nodes may cause the chrony sources to be marked offline causing synchronization to not occur. Related Bug 2040915 Version-Release number of selected component (if applicable): OSP16.2/OSP16.1
chrony-online and chronyd are both started after a reboot: [heat-admin@compute-0 ~]$ sudo systemctl status chrony-online ● chrony-online.service - chronyd online sources service Loaded: loaded (/etc/systemd/system/chrony-online.service; enabled; vendor preset: disabled) Active: inactive (dead) since Wed 2022-11-02 20:43:09 UTC; 15min ago Main PID: 2459 (code=exited, status=0/SUCCESS) Nov 02 20:43:09 compute-0 systemd[1]: Starting chronyd online sources service... Nov 02 20:43:09 compute-0 chronyc[2459]: 200 OK Nov 02 20:43:09 compute-0 systemd[1]: Started chronyd online sources service. [heat-admin@compute-0 ~]$ sudo systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-11-02 20:42:35 UTC; 23min ago Docs: man:chronyd(8) man:chrony.conf(5) Main PID: 959 (chronyd) Tasks: 1 (limit: 49478) Memory: 2.8M CGroup: /system.slice/chronyd.service └─959 /usr/sbin/chronyd Nov 02 20:42:35 compute-0 systemd[1]: Starting NTP client/server... Nov 02 20:42:35 compute-0 chronyd[959]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +I> Nov 02 20:42:35 compute-0 chronyd[959]: Frequency -6.363 +/- 0.028 ppm read from /var/lib/chrony/drift Nov 02 20:42:35 compute-0 systemd[1]: Started NTP client/server. Nov 02 20:43:13 compute-0 chronyd[959]: Selected source 10.11.160.238
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.9 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8795
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days