(In reply to Reinhard Max from comment #7) > This might better be discussed with upstream. Is that something I should do, or a suggestion for the chrony maintainer? It may be chrony working as designed, but the way it's implemented in Tumbleweed could be leading to the observed behaviour -- which could therefore be resolved with a different Tumbleweed config.