Project

General

Profile

Actions

Bug #14796

closed

test/osd/osd-markdown.sh has too-aggressive timing restrictions

Added by Dan Mick about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Actions #1

Updated by Dan Mick about 8 years ago

test/osd/osd-markdown.sh's tests try to set the OSD markdown count and period to 5 and 40s, and then mark the OSD down 6 times over 40s, waiting for (40/6)s after each mark down, and expecting the OSD to stay up except for the last markdown.

This requires that the osd respond too quickly and reliably, IMO. It would be better, I think, to have a fixed per-iteration sleeptime, so that the markdowns could comfortably occur within the given time interval, and to make sure the time interval is comfortably longer than "count * sleeptime", so that delays in issuing any of the commands (the actual 'down' command or the osd tree commands) don't cause the period to expire.

Actions #2

Updated by Dan Mick about 8 years ago

  • Status changed from New to Fix Under Review
  • Source changed from other to Development
Actions #3

Updated by Dan Mick about 8 years ago

  • Assignee set to Dan Mick
Actions #4

Updated by Dan Mick about 8 years ago

  • Status changed from Fix Under Review to Resolved

98b6d91288ebea17c3872d4d86e56beadcf0c8c4 in jewel and master

Actions

Also available in: Atom PDF