For a while now, after reboot of tumbleweed VMs, I see chronyd failing to
start. Starting it by hand once I notice, works fine.

journal shows:

Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Start operation timed
out. Terminating.
Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Unit entered failed
state.
Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Failed with result
'timeout'.

The issue is not reproducable - it just fails after some reboots.

/etc/chrony.conf does not contain hostnames, just some (local) servers
specified by IP address.