Actions
Bug #10675
closedfailures related to clock skew
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure Service
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
I suspect ntp is acting up in sepia. There are quite a few job failures related to clock skew. Clock skew could also explain why teuthology decided to use stale pycs in issue #10651
Look at the failures on this fun for an example:
"2015-01-28 08:04:30.278152 mon.0 10.214.132.17:6789/0 3 : cluster [WRN] message from mon.1 was stamped 1.988812s in the future, clocks not synchronized" in cluster log
Actions