Bug 1381445 - Posix_compliance test suite fails with latest 3.2 builds.
Summary: Posix_compliance test suite fails with latest 3.2 builds.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: RHGS 3.2.0
Assignee: Jiffin
QA Contact: Arthy Loganathan
URL:
Whiteboard:
Depends On:
Blocks: 1351528
TreeView+ depends on / blocked
 
Reported: 2016-10-04 06:49 UTC by Shashank Raj
Modified: 2017-03-23 06:23 UTC (History)
10 users (show)

Fixed In Version: nfs-ganesha-2.4.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 06:23:57 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0493 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.2.0 nfs-ganesha bug fix and enhancement update 2017-03-23 09:19:13 UTC

Description Shashank Raj 2016-10-04 06:49:56 UTC 
Description of problem:

Posix_compliance test suite fails with latest 3.2 builds. 

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

[root@dhcp42-59 ~]# rpm -qa|grep ganesha
nfs-ganesha-2.4.0-2.el6rhs.x86_64
nfs-ganesha-gluster-2.4.0-2.el6rhs.x86_64
glusterfs-ganesha-3.8.4-2.el6rhs.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Create a nfs-ganesha cluster, create a volume and enable ganesha on it.
2. Mount the volume via ver=4 on client.
3. Run posix_compliance test suite and observe that below failures are observed:

===========================TESTS RUNNING===========================
Changing to the specified mountpoint
/mnt/nfs1/run17555
executing posix_compliance
start: 15:13:23
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chmod/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chmod/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chown/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chown/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chown/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/chown/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/link/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/link/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
/opt/qa/tools/posix-testsuite/tests/mkfifo/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
/opt/qa/tools/posix-testsuite/tests/mkfifo/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
/opt/qa/tools/posix-testsuite/tests/mkfifo/../misc.sh: line 100: [: ENOENT: integer expression expected
lstat returned -1
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/rename/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/rename/../misc.sh: line 100: [: ENOENT: integer expression expected
lstat returned -1
lstat returned -1
lstat returned -1
lstat returned -1
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/unlink/../misc.sh: line 100: [: ENOENT: integer expression expected
stat returned -1
stat returned -1
/opt/qa/tools/posix-testsuite/tests/unlink/../misc.sh: line 100: [: ENOENT: integer expression expected

real	33m26.048s
user	0m5.990s
sys	0m11.532s
/opt/qa/tools/posix-testsuite/tests/chflags/00.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/01.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/02.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/03.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/04.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/05.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/06.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/07.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/08.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/09.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/10.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/11.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/12.t ... ok
/opt/qa/tools/posix-testsuite/tests/chflags/13.t ... ok
/opt/qa/tools/posix-testsuite/tests/chmod/00.t ..... 
Failed 13/58 subtests 
/opt/qa/tools/posix-testsuite/tests/chmod/01.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/02.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/03.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/04.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/05.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/06.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/07.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/08.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/09.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/10.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chmod/11.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/00.t ..... 
Failed 27/171 subtests 
/opt/qa/tools/posix-testsuite/tests/chown/01.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/02.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/03.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/04.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/05.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/06.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/07.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/08.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/09.t ..... ok
/opt/qa/tools/posix-testsuite/tests/chown/10.t ..... ok
/opt/qa/tools/posix-testsuite/tests/link/00.t ...... 
Failed 32/82 subtests 
/opt/qa/tools/posix-testsuite/tests/link/01.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/02.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/03.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/04.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/05.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/06.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/07.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/08.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/09.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/10.t ...... 
Failed 2/14 subtests 
/opt/qa/tools/posix-testsuite/tests/link/11.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/12.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/13.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/14.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/15.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/16.t ...... ok
/opt/qa/tools/posix-testsuite/tests/link/17.t ...... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/00.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/01.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/02.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/03.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/04.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/05.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/06.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/07.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/08.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/09.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/10.t ..... 
Failed 3/12 subtests 
/opt/qa/tools/posix-testsuite/tests/mkdir/11.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkdir/12.t ..... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/00.t .... 
Failed 31/36 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/01.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/02.t .... 
Failed 2/3 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/03.t .... 
Failed 2/11 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/04.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/05.t .... 
Failed 4/12 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/06.t .... 
Failed 4/12 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/07.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/08.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/09.t .... 
Failed 3/12 subtests 
/opt/qa/tools/posix-testsuite/tests/mkfifo/10.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/11.t .... ok
/opt/qa/tools/posix-testsuite/tests/mkfifo/12.t .... ok
/opt/qa/tools/posix-testsuite/tests/open/00.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/01.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/02.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/03.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/04.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/05.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/06.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/07.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/08.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/09.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/10.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/11.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/12.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/13.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/14.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/15.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/16.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/17.t ...... 
Failed 3/3 subtests 
/opt/qa/tools/posix-testsuite/tests/open/18.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/19.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/20.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/21.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/22.t ...... 
Failed 2/12 subtests 
/opt/qa/tools/posix-testsuite/tests/open/23.t ...... ok
/opt/qa/tools/posix-testsuite/tests/open/vb.t ...... ok
/opt/qa/tools/posix-testsuite/tests/rename/00.t .... 
Failed 24/79 subtests 
/opt/qa/tools/posix-testsuite/tests/rename/01.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/02.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/03.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/04.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/05.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/06.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/07.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/08.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/09.t .... 
Failed 12/56 subtests 
/opt/qa/tools/posix-testsuite/tests/rename/10.t .... 
Failed 29/188 subtests 
/opt/qa/tools/posix-testsuite/tests/rename/11.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/12.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/13.t .... 
Failed 11/17 subtests 
/opt/qa/tools/posix-testsuite/tests/rename/14.t .... 
Failed 4/17 subtests 
/opt/qa/tools/posix-testsuite/tests/rename/15.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/16.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/17.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/18.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/19.t .... ok
/opt/qa/tools/posix-testsuite/tests/rename/20.t .... 
Failed 5/16 subtests 
/opt/qa/tools/posix-testsuite/tests/rmdir/00.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/01.t ..... 
Failed 3/14 subtests 
/opt/qa/tools/posix-testsuite/tests/rmdir/02.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/03.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/04.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/05.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/06.t ..... 
Failed 4/20 subtests 
/opt/qa/tools/posix-testsuite/tests/rmdir/07.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/08.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/09.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/10.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/11.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/12.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/13.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/14.t ..... ok
/opt/qa/tools/posix-testsuite/tests/rmdir/15.t ..... ok
/opt/qa/tools/posix-testsuite/tests/symlink/00.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/01.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/02.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/03.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/04.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/05.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/06.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/07.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/08.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/09.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/10.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/11.t ... ok
/opt/qa/tools/posix-testsuite/tests/symlink/12.t ... ok
/opt/qa/tools/posix-testsuite/tests/truncate/00.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/01.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/02.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/03.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/04.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/05.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/06.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/07.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/08.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/09.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/10.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/11.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/12.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/13.t .. ok
/opt/qa/tools/posix-testsuite/tests/truncate/14.t .. ok
/opt/qa/tools/posix-testsuite/tests/unlink/00.t .... 
Failed 16/55 subtests 
/opt/qa/tools/posix-testsuite/tests/unlink/01.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/02.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/03.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/04.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/05.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/06.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/07.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/08.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/09.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/10.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/11.t .... 
Failed 9/33 subtests 
/opt/qa/tools/posix-testsuite/tests/unlink/12.t .... ok
/opt/qa/tools/posix-testsuite/tests/unlink/13.t .... ok

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chmod/00.t   (Wstat: 0 Tests: 58 Failed: 13)
  Failed tests:  12-16, 33-36, 45-48
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 27)
  Failed tests:  8-13, 77, 104-108, 126-132, 147-150, 163-166
/opt/qa/tools/posix-testsuite/tests/link/00.t    (Wstat: 0 Tests: 82 Failed: 32)
  Failed tests:  28-42, 44-46, 48, 50, 61-67, 75-78, 81
/opt/qa/tools/posix-testsuite/tests/link/10.t    (Wstat: 0 Tests: 14 Failed: 2)
  Failed tests:  11-12
/opt/qa/tools/posix-testsuite/tests/mkdir/10.t   (Wstat: 0 Tests: 12 Failed: 3)
  Failed tests:  10-12
/opt/qa/tools/posix-testsuite/tests/mkfifo/00.t  (Wstat: 0 Tests: 36 Failed: 31)
  Failed tests:  2-16, 18-23, 25-27, 29-35
/opt/qa/tools/posix-testsuite/tests/mkfifo/02.t  (Wstat: 0 Tests: 3 Failed: 2)
  Failed tests:  1-2
/opt/qa/tools/posix-testsuite/tests/mkfifo/03.t  (Wstat: 0 Tests: 11 Failed: 2)
  Failed tests:  5-6
/opt/qa/tools/posix-testsuite/tests/mkfifo/05.t  (Wstat: 0 Tests: 12 Failed: 4)
  Failed tests:  4-5, 9-10
/opt/qa/tools/posix-testsuite/tests/mkfifo/06.t  (Wstat: 0 Tests: 12 Failed: 4)
  Failed tests:  4-5, 9-10
/opt/qa/tools/posix-testsuite/tests/mkfifo/09.t  (Wstat: 0 Tests: 12 Failed: 3)
  Failed tests:  10-12
/opt/qa/tools/posix-testsuite/tests/open/17.t    (Wstat: 0 Tests: 3 Failed: 3)
  Failed tests:  1-3
/opt/qa/tools/posix-testsuite/tests/open/22.t    (Wstat: 0 Tests: 12 Failed: 2)
  Failed tests:  7-8
/opt/qa/tools/posix-testsuite/tests/rename/00.t  (Wstat: 0 Tests: 79 Failed: 24)
  Failed tests:  22-24, 26-31, 33-35, 49, 53, 55-58, 61
                69, 71-74
/opt/qa/tools/posix-testsuite/tests/rename/09.t  (Wstat: 0 Tests: 56 Failed: 12)
  Failed tests:  23-25, 27-29, 31-33, 35-37
/opt/qa/tools/posix-testsuite/tests/rename/10.t  (Wstat: 0 Tests: 188 Failed: 29)
  Failed tests:  12, 27, 42, 83-85, 89-90, 95, 98-100, 104-105
                110, 113-115, 119-120, 125, 128-130, 132-133
                144, 159, 174
/opt/qa/tools/posix-testsuite/tests/rename/13.t  (Wstat: 0 Tests: 17 Failed: 11)
  Failed tests:  7-17
/opt/qa/tools/posix-testsuite/tests/rename/14.t  (Wstat: 0 Tests: 17 Failed: 4)
  Failed tests:  7-8, 10-11
/opt/qa/tools/posix-testsuite/tests/rename/20.t  (Wstat: 0 Tests: 16 Failed: 5)
  Failed tests:  9-11, 13, 16
/opt/qa/tools/posix-testsuite/tests/rmdir/01.t   (Wstat: 0 Tests: 14 Failed: 3)
  Failed tests:  12-14
/opt/qa/tools/posix-testsuite/tests/rmdir/06.t   (Wstat: 0 Tests: 20 Failed: 4)
  Failed tests:  17-20
/opt/qa/tools/posix-testsuite/tests/unlink/00.t  (Wstat: 0 Tests: 55 Failed: 16)
  Failed tests:  10-12, 19-23, 28-31, 39-42
/opt/qa/tools/posix-testsuite/tests/unlink/11.t  (Wstat: 0 Tests: 33 Failed: 9)
  Failed tests:  14-22
Files=185, Tests=1962, 2006 wallclock secs ( 0.61 usr  0.17 sys +  5.32 cusr 11.33 csys = 17.43 CPU)
Result: FAIL
end: 15:46:51
removed posix compliance directories
1
Total 1 tests were successful
Switching over to the previous working directory
Removing /mnt/nfs1/run17555/


Actual results:

Posix_compliance test suite fails with latest 3.2 builds. 

Expected results:

There should not be any failures.

Additional info:
Comment 6 Frank Filz 2016-11-04 16:28:29 UTC 
What version of these tests are being run?

I have several fixes for the test suite on github to get around client side issues.

I'd like more details on the failing tests, I have all tests passing on FSAL_VFS and FSAL_CEPH in Ganesha 2.4.1, so if there are any failures remaining they are most likely Gluster or FSAL_GLUSTER specific issues.
Comment 8 Frank Filz 2016-11-07 16:37:43 UTC 
Ah, so it is a version of pjdfstests... I'm going to try comparing it to the versions I have been using just to see where it's different and where it's the same...

I wish there was a good central community repo for this test suite, there seem to be several slightly different versions out there...
Comment 9 Jiffin 2016-11-07 18:51:17 UTC 
On latest build only two of test case is failing(see comment 4 and 5), one is bug in a test suite and another is not easy to fix(may require complex changes). Hence changing the bug in ON_QA. Please free to open up a new bug for open07.t failure if needed.
Comment 10 Frank Filz 2016-11-07 19:01:23 UTC 
I've had a bit of a look, this looks to be a pretty old version of the tests.

Please consider looking at the more up to date pjdfstests:

https://github.com/pjd/pjdfstest

I have some updates to that repo here:

https://github.com/ffilz/pjdfstest

There's also another version I have:

https://github.com/ffilz/ntfs-3g-pjd-fstest

I will run the version from above against FSAL_VFS on latest code and see if it shows any errors there, and analyze from there.
Comment 13 Frank Filz 2016-11-17 17:24:45 UTC 
Ok, I've had a look at the wireshark trace for the open07 failure.

I think it's a client problem.

Here is the basic code sequence and what I see in the trace to match:

expect 0 -u 1000 -g 1000 create ${n1} 0644

OPEN4, CLAIM_NULL, OPEN4_CREATE, EXCLUSIVE4
SETATTR mode 0644, time access to server time, time modify to server time

expect 0 -u 1000 -g 1000 chmod ${n1} 0477

SETATTR mode 0477

expect EACCES -u 1000 -g 1000 open ${n1} O_RDONLY,O_TRUNC

OPEN4, CLAIM_NULL, NO_CREATE, OPEN4_SHARE_ACCESS_READ

The O_TRUNC never results in an attempt to set the file size attribute, nor is any ACCESS4 call made to check for write access, so there is no way for Ganesha to disallow the truncate.

I think actually the client sees the size is already zero, so it doesn't try and do anything with the truncate, but the POSIX standard still requires the open call to be rejected in this case.

What is the test client? There have been bug fixes in this area in the client, though I can not put my finger on one (there was one I remembered that does not apply that allowed a client to open an execute only file for read).
Comment 14 Arthy Loganathan 2016-11-18 03:50:47 UTC 
With the latest build, 
nfs-ganesha-2.4.1-1.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64

the following tests got failed for volume with lesser number of bricks( plain distribute with 2 bricks and 1*2)

Test Summary Report
-------------------

vers=3:
--------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 1)
  Failed test:  77
Files=185, Tests=1962, 105 wallclock secs ( 1.46 usr  0.40 sys + 15.38 cusr 28.33 csys = 45.57 CPU)
Result: FAIL
end: 19:44:32
removed posix compliance directories
1
Total 1 tests were successful
Switching over to the previous working directory
Removing /mnt/test_nfs/run19715/


vers 4:
--------

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 1)
  Failed test:  77
/opt/qa/tools/posix-testsuite/tests/open/07.t    (Wstat: 0 Tests: 23 Failed: 3)
  Failed tests:  5, 7, 9
Files=185, Tests=1962, 106 wallclock secs ( 1.44 usr  0.43 sys + 15.51 cusr 28.07 csys = 45.45 CPU)
Result: FAIL
end: 19:49:01
removed posix compliance directories
1
Total 1 tests were successful
Switching over to the previous working directory

Could you confirm and update the bug if these are known failures.

Also, in 6*2 volume, nfs ganesha process got omm killed on the mounted node. Bug : https://bugzilla.redhat.com/show_bug.cgi?id=1381452
Comment 15 Frank Filz 2016-11-18 04:18:27 UTC 
Again, what version of Linux is the client? RHEL? Which version?

I'm pretty sure the open/07.t failure is a client bug.

It would help to isolate the one chown/00.t test that is failing.
Comment 16 Jiffin 2016-11-18 04:40:59 UTC 
(In reply to Frank Filz from comment #15)
> Again, what version of Linux is the client? RHEL? Which version?
> 

I have ran it on kernel 4.7.10-100.fc23.x86_64 (fedora23 machine) and I guess have Arthy/Shashank has ran it on rhel 7.3

As you suggested I can see this failure in knfs as well

> I'm pretty sure the open/07.t failure is a client bug.
> 
> It would help to isolate the one chown/00.t test that is failing.

This one related to issue in script. See comment4 for more details.

Since one issue is related to client and another is related to test script I request Arthy to close this bug
Comment 18 Arthy Loganathan 2016-11-18 12:03:21 UTC 
Since the two tests that failed are related to test scripts and client and the remaining issues are fixed and passing in the latest build, 
nfs-ganesha-2.4.1-1.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-5.el7rhgs.x86_64
moving this bug to verified state.
Comment 19 Frank Filz 2016-11-18 16:37:53 UTC 
On chown/00.t - ok, some file systems don't clear the SGID bit when owner is changed with chown, see this text from man 2 chown:


When the owner or group of an executable file are changed by an unprivileged user the S_ISUID and S_ISGID mode bits are cleared.  POSIX does not  specify  whether  this also  should  happen  when  root  does  the  chown(); the Linux behavior depends on the kernel version.  In case of a non-group-executable file (i.e., one for which the S_IXGRP bit is not set) the S_ISGID bit indicates mandatory locking, and is not cleared by a chown().

On the other hand, this chown is being done as non-root, so we should actually do something in Ganesha (perhaps in the FSALs) to make sure the chown does indeed clear SGID.

I think this passes on FSAL_VFS because in my setup, a chown done by root DOES clear SGID.

So we may need to look into what is happening with non-root chown in Gluster or FSAL_GLUSTER.

We should open a client bug for the open problem.

Also, if you update the test, please look at my github repo above. There were some changes I made to get around a few things, and it is based on the most current version of these tests I found.
Comment 21 errata-xmlrpc 2017-03-23 06:23:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2017-0493.html
Note You need to log in before you can comment on or make changes to this bug.