http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c64

Josef Reidinger jreidinger@suse.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(max@suse.com)

--- Comment #64 from Josef Reidinger jreidinger@suse.com --- Reinhard - I test potential change in yast with proposing to default ntp server option "offline" which should mark source as offline and then network dispatcher can activate it ( e.g. NM in /etc/NetworkManager/dispatcher.d/20-chrony ). But sadly it does not work and it still waiting when I am testing it (instead of using rtc when all ntp servers are marked as offline).

Enabling chrony-wait based on availability of network is also tricky as e.g. notebooks can have network when installed and then travelling without network.

So do you really see disabling chrony-wait as only option here for YaST how to short-term fix it? ( of course plan is that we add option to control.xml if product require precise time and if so, then it will still enabled e.g. for Kubic ).