Comment 1 for bug 1924922

Hello Adam and thanks for this bug report. Does chrony actually set the system time after a while, or is this a permanent failure of chrony as an NTP client? In other words, is chrony set up correctly and this is a race-like issue between chrony and ssh-import-id, or is chrony broken on the system after cloud-init set it up? Does it work with a different ntp_client (e.g. systemd-timesyncd)?

Could you please run `cloud-init collect-logs` on a system where you hit the issue and attach the generated tarball to this bug report?

Waiting for more information I'm setting this to Incomplete for the moment.