[Bugs] [Bug 1618915] New: Spurious failure in tests/basic/ec/ec-1468261.t

bugzilla at redhat.com bugzilla at redhat.com
Sat Aug 18 07:32:26 UTC 2018


            Bug ID: 1618915
           Summary: Spurious failure in tests/basic/ec/ec-1468261.t
           Product: GlusterFS
           Version: mainline
         Component: tests
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org

Description of problem:
 I found that tests/basic/ec/ec-1468261.t is timing out because of the change
in heal-timeout to 10 minutes from 1 minute in this patch. I changed it to 1
minute in this patch. But after that I am running into another issue because of
the recent change in kill_brick() implementation.

The test at line 38 creates a new file and immediately kills two bricks and
checks that trusted.ec.dirty xattr is non-zero for the bricks. But what ends up
happening is that even before the brick is down, the post-op happens, leading
to failure of the test.

[2018-08-16 08:14:38.384004]:++++++++++ G_LOG:tests/basic/ec/ec-1468261.t:
TEST: 38 touch /mnt/glusterfs/0/test_dir/new_file ++++++++++
[2018-08-16 08:14:38.576104]:++++++++++ G_LOG:tests/basic/ec/ec-1468261.t:
TEST: 39 kill_brick patchy localhost.localdomain /d/backends/patchy0 ++++++++++
[2018-08-16 08:14:39.723034] I [ec-common.c:2409:ec_unlock_now] 0-UNLOCKING:

****** Post-op and Unlock on the directory happened in the line above after
that the disconnect happened below ******

[2018-08-16 08:14:39.766402] W [socket.c:731:__socket_rwv] 0-patchy-client-0:
readv on failed (No data available) 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list