Clock skew on testbeds
Bug #1880839 reported by
Balint Reczey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Won't Fix
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Clock stepped backward on a testbed:
...
context FAIL stderr: make[2]: Warning: File '/tmp/tmp.
autopkgtest [13:55:37]: test context: - - - - - - - - - - stderr - - - - - - - - - -
make[2]: Warning: File '/tmp/tmp.
make[2]: warning: Clock skew detected. Your build may be incomplete.
..
Related branches
~rbalint/autopkgtest-cloud:more-retries
- Iain Lane: Approve
-
Diff: 156 lines (+65/-53)1 file modifiedworker/worker (+65/-53)
Changed in systemd (Ubuntu): | |
status: | New → Won't Fix |
Changed in auto-package-testing: | |
status: | New → Won't Fix |
To post a comment you must log in.
My suspect is systemd-timesyncd:
See src/timesync/ timesyncd- manager. c:
/*
* Maximum delta in seconds which the system clock is gradually adjusted
* (slewed) to approach the network time. Deltas larger that this are set by
* letting the system time jump. The kernel's limit for adjtime is 0.5s.
*/
#define NTP_MAX_ADJUST 0.4
I suspect the boost compilation's load made the internal clock diverge enough for systemd to jump the time.
The default PollIntervalMaxSec is 2048 seconds in systemd.
I can reduce it in systemd, but there is a jump as high as 0.85 in /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- focal/focal/ amd64/b/ boost1. 71/20200317_ 211804_ 626ff@/ log.gz
https:/
which could not have been prevented by just halving the default.
How about changing the autopkgtest setup to either change a default or disable systemd-timesyncd or install chrony instead?