Bug #6905
closednightlies: failed to become clean before timeout expired
0%
Description
this happened running rados test on master branch
logs: ubuntu@teuthology:/a/teuthology-2013-11-25_23:00:04-rados-master-testing-basic-plana/118522
Updated by Sage Weil over 10 years ago
- Status changed from New to 12
- Assignee set to David Zafman
/a/teuthology-2013-12-17_23:00:03-rados-next-distro-basic-plana/7188
Updated by David Zafman over 10 years ago
I've run the particular yaml file with increased OSD debugging multiple times. It does not reproduce. I do notice that there are still pushes going on as late as "2013-12-18 03:18:33.552116" in an OSD log and the timeout occurred at 2013-12-18T03:18:34.260 according to teuthology.log.
Could it be the case that in some random thrashing scenarios we just can't meet the test case recovery timeout?
Updated by Sage Weil over 10 years ago
David Zafman wrote:
I've run the particular yaml file with increased OSD debugging multiple times. It does not reproduce. I do notice that there are still pushes going on as late as "2013-12-18 03:18:33.552116" in an OSD log and the timeout occurred at 2013-12-18T03:18:34.260 according to teuthology.log.
Could it be the case that in some random thrashing scenarios we just can't meet the test case recovery timeout?
Could be.. should we just add 50% to the timeout and see if it comes up again?
Updated by David Zafman over 10 years ago
My previous comment indicating that a clean timeout occurred while recovery was still gong on applied to /a/teuthology-2013-12-17_23:00:03-rados-next-distro-basic-plana/7188
/a/teuthology-2013-11-25_23:00:04-rados-master-testing-basic-plana/118522 in the original description is actually a duplicate of bug #6685.