Bug 1427545

Summary: sparse-file-self-heal test fails sometimes
Product: [Community] GlusterFS Reporter: nh2 <nh2-redhatbugzilla>
Component: testsAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED EOL QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 3.10CC: bugs, nh2-redhatbugzilla
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-20 18:30:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sparse-file-self-heal fails
none
sparse-file-self-heal succeeds
none
gluster-sparse-file-self-heal-loop.txt.gz none

Description nh2 2017-02-28 14:48:21 UTC
Created attachment 1258396 [details]
sparse-file-self-heal fails

'm running the tests in Vagrant on 3.10, twice in a row:

First time sparse-file-self-heal fails (see attachment)

Result: FAIL
./tests/basic/afr/sparse-file-self-heal.t: bad status 1


Second time it succeeds (see attachment):

Result: PASS
End of test ./tests/basic/afr/sparse-file-self-heal.t

Comment 1 nh2 2017-02-28 14:48:58 UTC
Created attachment 1258397 [details]
sparse-file-self-heal succeeds

Comment 2 nh2 2017-02-28 14:49:47 UTC
I found this issue together with issue https://bugzilla.redhat.com/show_bug.cgi?id=1427540

Comment 3 nh2 2017-03-03 10:58:21 UTC
Created attachment 1259486 [details]
gluster-sparse-file-self-heal-loop.txt.gz

OK, I've run now:

[root@vagrant-testVM glusterfs]# while true; do prove -v tests/basic/afr/sparse-file-self-heal.t; done

So far, this test has passed 2811 times, and failed 47 times, so the probability of this test failing is ~ 1.6 %.

I have attached a the log of my command above.

Notably, when the test failed, it failed 47 times in a row, so I suspect that it happens when certain conditions temporarily hold on the test systems, such as busy disk or busy CPU.

Comment 4 Shyamsundar 2018-06-20 18:30:06 UTC
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.