Bug #6905
closed
nightlies: failed to become clean before timeout expired
Added by Tamilarasi muthamizhan over 10 years ago.
Updated over 10 years ago.
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
- 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
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?
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?
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.
- Status changed from 12 to Duplicate
Also available in: Atom
PDF