[Bugs] [Bug 1672480] New: Bugs Test Module tests failing on s390x

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1672480

            Bug ID: 1672480
           Summary: Bugs Test Module tests failing on s390x
           Product: GlusterFS
           Version: 4.1
          Hardware: s390x
                OS: Linux
            Status: NEW
         Component: tests
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: abhaysingh1722 at yahoo.in
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
Observing test failures for the following test cases:-
./tests/bugs/glusterfs/bug-902610.t
./tests/bugs/posix/bug-1619720.t
./tests/bitrot/bug-1207627-bitrot-scrub-status.t

After analyzing the above test failures, we have observed that the hash values
for the bricks and files are getting differently calculated on s390x systems as
compared to those on x86.

As per the documentation given at
https://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/dht/ ,
To place a file in a directory, a hash is calculated for the file using both
the (containing) directory's unique GFID and the file's name.This hash is then
matched to one of the layout assignments, to yield the hashed location.
However, on s390x, certain files have hash values that are beyond the hash
range of the available bricks. Therefore, these files don't get located in
their respective hashed locations.

This has been observed in other test cases too. 
For example, ./tests/bugs/distribute/bug-1161311.t,
./tests/bugs/distribute/bug-1193636.t, ./tests/basic/namespace.t.


Is there any workaround to get the correct hashed locations for the files?

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


How reproducible:
Build Glusterfs v4.1.5 and run the test case with ./run-tests.sh prove -vf
<testcase_name>

Steps to Reproduce:
1.
2.
3.

Actual results:
Tests FAIL

Expected results:
Tests should PASS


Additional info:

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