Comment # 63 on bug 1145193 from Reinhard Max

Please stop this, Ravas, you are running completely into the wrong direction
and cluttering this already messy bug report even more.

If there are services running on a system that require a synchronised time
there is no way around chrony-wait.service (or anything else that blocks untill
the time is in sync), because anything else that you are suggesting would
continue booting with unsynchronized time.

So, disabling chrony-wait.service can only be a short-term workaround (on which
the YaST team is working right now), but the final goal (as I have stated
several time already) has to be to minimize the set of services that depend on
time-sync.target and to make sure nothing depends on it that is on the
dependency path to an interactive session.

Again, please top this unhelpful discussion about alternatives to having
"waitsync" in chrony-wait.service, because there are no.