Project

General

Profile

Actions
Copy link

Bug #10712

closed

TestFlush intermittent failure on scatter_writebehind event

Added by John Spray about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
John Spray
Category:
-
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The flush code isn't fully deterministic, sometimes the single log segment left behind just has a subtreemap event, and sometimes there is an extra scatter_writebehind in there too.

Either make the code deterministic or make the test tolerant.

Actions
Copy link
 #2

Updated by Sage Weil about 9 years ago

  • Priority changed from Normal to Urgent

urgent by default since this causes qa tests to fail

Actions
Copy link
 #3

Updated by Sage Weil about 9 years ago

  • Source changed from other to Q/A
Actions
Copy link
 #4

Updated by John Spray about 9 years ago

  • Status changed from New to 7

Updating the test to tolerate this condition, as it's a valid outcome from flush

Actions
Copy link
 #5

Updated by John Spray about 9 years ago

  • Status changed from 7 to Fix Under Review
Actions
Copy link
 #6

Updated by John Spray about 9 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link
 #7

Updated by Loïc Dachary almost 9 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to hammer
Actions
Copy link
 #9

Updated by Loïc Dachary almost 9 years ago

  • Status changed from Pending Backport to Resolved
  • Regression set to No
Actions
Copy link

Also available in: Atom PDF