Project

General

Profile

Actions
Copy link

Bug #19255

closed

qa: test_full_fclose failure

Added by John Spray about 7 years ago. Updated about 6 years ago.

Status:
Can't reproduce
Priority:
Urgent
Assignee:
-
Category:
Testing
Target version:
-
% Done:

0%

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

Description

I suspect the rework of full handling broke this test:
https://github.com/ceph/ceph/pull/13615/files

It's failing at this point:

270             # OK, now we should sneak in under the full condition               
271             # due to the time it takes the OSDs to report to the                
272             # mons, and get a successful fsync on our full-making data          
273             os.fsync(f)                                                         
274             print "successfully fsync'ed prior to getting full state reported"

So perhaps the new fullness handling code in RADOS is snappier than the old code was.

Actions
Copy link
 #1

Updated by Patrick Donnelly over 6 years ago

  • Status changed from New to Need More Info

John, do you have a test failure to point to?

Actions
Copy link
 #2

Updated by Patrick Donnelly about 6 years ago

  • Subject changed from test_full_fclose failure to qa: test_full_fclose failure
  • Status changed from Need More Info to Can't reproduce
  • Target version deleted (v12.0.0)
  • Source set to Development
  • Tags set to qa
Actions
Copy link

Also available in: Atom PDF