http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c62 --- Comment #62 from ravas mi <ravas@tuta.io> --- It looks like NetworkManager does DNS related things _after_ chrony starts. I see that "Could not resolve address of initstepslew server <URL>." directly follows chrony starting, and then shortly after that I see

NetworkManager[1098]: <info> [1569905050.7145] dns-mgr[0x555d0a1ca210]: init: dns=default,systemd-resolved rc-manager=netconfig

It seems like if we could ensure that DNS stuff happens prior to chrony starting, then "initstepslew" could replace chrony-wait, assuming "initstepslew" accepts a pool's URL (i.e. 3.opensuse.pool.ntp.org). That said, disabling chrony-wait and using "makestep 0.1 1" seems to work fine for my purposes, but then I don't know if I even benefit from the stepping. -- You are receiving this mail because: You are on the CC list for the bug.