Actions
Bug #11782
closedlab clocks not reliably synced
Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
For example:
http://qa-proxy.ceph.com/teuthology/teuthology-2015-05-20_23:04:01-fs-master-testing-basic-multi/902894/
plana38's clock is half a second out.
Preferably we would not schedule tests on nodes with bad clocks -- as well as obvious errors like that in this test, it can cause much more subtle issues too.
Updated by Loïc Dachary almost 9 years ago
- Project changed from Ceph to sepia
- Category deleted (
qa)
Updated by John Spray almost 9 years ago
magna clocks not synced either, lots of time failures here: http://pulpito.ceph.redhat.com/teuthology-2015-07-15_18:04:02-fs-hammer---basic-magna/
Updated by John Spray almost 9 years ago
teuthology-2015-07-15_18:10:02-knfs-hammer-testing-basic-magna/153963
Updated by Dan Mick about 8 years ago
- Status changed from New to Can't reproduce
If it gets worse again, we can try adding clock.sync to internal tasks, but it seems to have gotten better somehow.
Actions