From 03e2693a7dc6cae292b80f83fe6a295b66f3e3df Mon Sep 17 00:00:00 2001 From: Sergey Orlov Date: Tue, 26 Mar 2019 18:31:34 +0100 Subject: [PATCH] ipatests: relax requirements for time server quality When synchronizing time with windows server using chronyd I often see error "No suitable source for synchronisation". This happens because chronyd with default options refuses to use time servers with big jitter and delay. For some reasons Windows time server does have big jitter. In some test setups delay also can be rathe big. Related to https://pagure.io/freeipa/issue/7889 Reviewed-By: Alexander Bokovoy --- ipatests/pytest_ipa/integration/tasks.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/ipatests/pytest_ipa/integration/tasks.py b/ipatests/pytest_ipa/integration/tasks.py index 459531c68..56cb451aa 100644 --- a/ipatests/pytest_ipa/integration/tasks.py +++ b/ipatests/pytest_ipa/integration/tasks.py @@ -801,8 +801,10 @@ def sync_time(host, server): host.run_command(['systemctl', 'stop', 'chronyd']) host.run_command(['chronyd', '-q', - "server {srv} iburst".format(srv=server.hostname), - 'pidfile /tmp/chronyd.pid', 'bindcmdaddress /']) + "server {srv} iburst maxdelay 1000".format( + srv=server.hostname), + 'pidfile /tmp/chronyd.pid', 'bindcmdaddress /', + 'maxdistance 1000', 'maxjitter 1000']) def connect_replica(master, replica, domain_level=None,