Actions
Bug #3854
closedmon: clock skew tests failing on master
Status:
Resolved
Priority:
Urgent
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
/a/sage-2013-01-17_12:29:29-rados-wip-3785-testing-basic 81 passes 644 FAIL scheduled_sage@flab collection:multimon clusters:21.yaml msgr-failures:few.yaml tasks:mon_clock_with_skews.yaml 182s 647 FAIL scheduled_sage@flab collection:multimon clusters:21.yaml msgr-failures:many.yaml tasks:mon_clock_with_skews.yaml 317s 650 FAIL scheduled_sage@flab collection:multimon clusters:3.yaml msgr-failures:few.yaml tasks:mon_clock_with_skews.yaml 93s 653 FAIL scheduled_sage@flab collection:multimon clusters:3.yaml msgr-failures:many.yaml tasks:mon_clock_with_skews.yaml 106s 656 FAIL scheduled_sage@flab collection:multimon clusters:6.yaml msgr-failures:few.yaml tasks:mon_clock_with_skews.yaml 138s 659 FAIL scheduled_sage@flab collection:multimon clusters:6.yaml msgr-failures:many.yaml tasks:mon_clock_with_skews.yaml 160s 662 FAIL scheduled_sage@flab collection:multimon clusters:9.yaml msgr-failures:few.yaml tasks:mon_clock_with_skews.yaml 158s 665 FAIL scheduled_sage@flab collection:multimon clusters:9.yaml msgr-failures:many.yaml tasks:mon_clock_with_skews.yaml 158s 679 FAIL scheduled_sage@flab collection:singleton all:osd-recovery-incomplete.yaml fs:btrfs.yaml msgr-failures:few.yaml 202s 680 FAIL scheduled_sage@flab collection:singleton all:osd-recovery-incomplete.yaml fs:btrfs.yaml msgr-failures:many.yaml 230s
Updated by Joao Eduardo Luis about 11 years ago
teuthology's wip-3854 commit:1d8640860441dc27e8342788c1ae17f5c1b3ccc0 fixes this issue.
Updated by Joao Eduardo Luis about 11 years ago
- Status changed from 12 to Fix Under Review
Updated by Sage Weil about 11 years ago
- Status changed from Fix Under Review to Resolved
pushed to master
Updated by Joao Eduardo Luis about 11 years ago
- Status changed from Resolved to 7
Happened again on QA, reopening while testing a new patch.
Updated by Joao Eduardo Luis about 11 years ago
This was fixed by d74b31b24db647a8b7c80d1552fa6f0b02c54ba4 and c54781618569680898e77e151dd7364f22ac4aa1
Actions