Actions
Bug #11514
closedTypica nodes are not reliably clock synced
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
^ that's one example, but we're seeing it a lot. The typica nodes aren't clock synced, or are jumping around, and it's causing tests to fail on log warnings (or occasionally on something a little less easy to skip, like timing-sensitive tests).
I know Dan looked at this some but I don't know if he came to any useful conclusions.
Updated by Greg Farnum almost 9 years ago
- Regression set to No
Here's one we're seeing pretty frequently: http://pulpito-rdu.front.sepia.ceph.com/teuthology-2015-05-05_23:14:01-samba-master-testing-basic-typica/11144/
2015-05-06T07:06:45.117 INFO:teuthology.orchestra.run.typica146.stdout: 2015-05-06T07:06:45.117 INFO:teuthology.orchestra.run.typica146.stdout:time: 2015-05-06 07:06:45.108907 2015-05-06T07:06:45.118 INFO:teuthology.orchestra.run.typica146.stdout:failure: defer_open [ 2015-05-06T07:06:45.118 INFO:teuthology.orchestra.run.typica146.stdout:child 1 (pid 23373) failed: Timing incorrect 3.84 violation 1 sec == 1.00 2015-05-06T07:06:45.118 INFO:teuthology.orchestra.run.typica146.stdout:] 2015-05-06T07:06:45.119 INFO:teuthology.orchestra.run.typica146.stderr:WARNING!: child 0 (pid 23372) failed: Timing incorrect 3.36 violation 1 sec == 1.00
Updated by David Galloway over 8 years ago
- Status changed from New to Won't Fix
Typica nodes have been relinquished to the CentOS Community so closing this issue as WONTFIX.
Actions