Looking at the RDS, chrony is disabled as per 

https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/edge_computing/sno-configure-for-vdu#ztp-sno-du-tuning-the-performance-patch_sno-configure-for-vdu 

via tuned 

(https://github.com/openshift-kni/cnf-features-deploy/blob/ac8dda5b7d4cef59b748dd8cb13f55a47da06cdf/ztp/source-crs/TunedPerformancePatch.yaml#L27 , 
however with 

https://github.com/openshift/machine-config-operator/commit/acf4a9d96e9cc295eaf7c122f65d246e467cfec8 

we added `chrony-wait.service` to the `Wants=` section of `kubelet-dependencies.target`. 

Via https://issues.redhat.com/browse/OCPBUGS-52831 the mc was changed in the docs so it removes chrony-wait.service from `kubelet-dependencies.target` when chrony is disabled, but it seems that didn't make it into the telco 
part and now, chrony wait service fails as it times out waiting for a 
disabled chrony ....

    OCP 4.18

Install and configure OCP as per edge docs, apply Tuned performance-patch, esp including `service.chronyd=stop,disable` after reboot check for chrony-wait.service failed time out

    1. Install OCP 4.18 
    2. Apply RDS as per docs esp including Tuned performance-patch from docs
    3. After reboot of the node check for chrony-wait.service failed on timeout     

[core@worker0 ~]$ systemctl status chrony-wait
× chrony-wait.service - Wait for chrony to synchronize system clock
     Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2025-08-14 07:49:17 UTC; 2h 8min ago
       Docs: man:chronyc(1)
   Main PID: 1697 (code=exited, status=1/FAILURE)
        CPU: 45ms

Aug 14 07:49:07 worker0 systemd[1]: Starting Wait for chrony to synchronize system clock...
Aug 14 07:49:17 worker0 systemd[1]: chrony-wait.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 07:49:17 worker0 systemd[1]: chrony-wait.service: Failed with result 'exit-code'.
Aug 14 07:49:17 worker0 systemd[1]: Stopped Wait for chrony to synchronize system clock.

status chrony-wait should not be in failed state when disabling chrony

see 

https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/machine_configuration/machine-configs-configure#cnf-disable-chronyd_machine-configs-configure  

The chrony disable mc also removes chrony-wait.service from `kubelet-dependencies.target` to avoid this issue