Bug 1505473 - Posix compliance rename test fails on fuse subdir mount
Summary: Posix compliance rename test fails on fuse subdir mount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: fuse
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: RHGS 3.3.1
Assignee: Amar Tumballi
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1475688 1505527
TreeView+ depends on / blocked
 
Reported: 2017-10-23 16:19 UTC by Manisha Saini
Modified: 2017-11-29 03:31 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.8.4-51
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1505527 (view as bug list)
Environment:
Last Closed: 2017-11-29 03:31:38 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3276 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-11-29 08:28:52 UTC

Description Manisha Saini 2017-10-23 16:19:15 UTC
Description of problem:
rename/00.t and rename/10.t tests in Posix compliance test suit are failing for fuse subdir mount

Version-Release number of selected component (if applicable):
glusterfs-3.8.4-50.el7rhgs.x86_64

How reproducible:
2/2

Steps to Reproduce:
1.Create 4*3 Distributed-Replicate volume
2.Mount the volume to fuse client
3.Create a directory inside the mount point
4.Set auth allow permission on the volume for that subdir
gluster v set ganeshavol1 auth.allow "/dir1(dhcp37-192.lab.eng.blr.redhat.com),/dir2(dhcp37-142.lab.eng.blr.redhat.com),/(*)"
5.Mount the subdir to same fuse client
6.Run posix compliance test suit on the subdir

Chown and rename test fails for subdir.
Chown test is a known failure for fuse volume mount (Fails on volume mounted via fuse as well)

Rename test pass on fuse volume mount but fails for fuse sub-dir mount

=================
Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 6)
  Failed tests:  84, 88, 141, 145, 149, 153
/opt/qa/tools/posix-testsuite/tests/rename/00.t  (Wstat: 0 Tests: 79 Failed: 8)
  Failed tests:  6, 11, 13, 20, 26, 31, 33, 44
/opt/qa/tools/posix-testsuite/tests/rename/10.t  (Wstat: 0 Tests: 188 Failed: 27)
  Failed tests:  11, 14, 19, 26, 29, 34, 41, 44, 49, 87
                90, 95, 102, 105, 110, 117, 120, 125, 139
                142, 147, 154, 157, 162, 169, 172, 177
Files=185, Tests=1962, 96 wallclock secs ( 0.78 usr  0.31 sys +  9.14 cusr 13.06 csys = 23.29 CPU)
Result: FAIL
end: 21:24:33
removed posix compliance directories
1
Total 1 tests were successful
Switching over to the previous working directory
Removing /mnt/fuse_mount1/run16899/
rmdir: failed to remove ‘/mnt/fuse_mount1/run16899/’: Directory not empty
rmdir failed:Directory not empty

===================

Actual results:
Rename test of posix compliance test suit fails for subdir

Expected results:
Rename test of posix compliance test suit should pass for subdir as well

Additional info:

Comment 2 Manisha Saini 2017-10-23 16:22:42 UTC
=====================
Fuse Volume Mount
=====================

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 6)
  Failed tests:  84, 88, 141, 145, 149, 153
Files=185, Tests=1962, 98 wallclock secs ( 0.83 usr  0.28 sys +  9.14 cusr 13.42 csys = 23.67 CPU)
Result: FAIL
end: 21:19:58
removed posix compliance directories
1
Total 1 tests were successful

====================
Fuse Subdir Mount
====================

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 6)
  Failed tests:  84, 88, 141, 145, 149, 153
/opt/qa/tools/posix-testsuite/tests/rename/00.t  (Wstat: 0 Tests: 79 Failed: 8)
  Failed tests:  6, 11, 13, 20, 26, 31, 33, 44
/opt/qa/tools/posix-testsuite/tests/rename/10.t  (Wstat: 0 Tests: 188 Failed: 27)
  Failed tests:  11, 14, 19, 26, 29, 34, 41, 44, 49, 87
                90, 95, 102, 105, 110, 117, 120, 125, 139
                142, 147, 154, 157, 162, 169, 172, 177
Files=185, Tests=1962, 96 wallclock secs ( 0.78 usr  0.31 sys +  9.14 cusr 13.06 csys = 23.29 CPU)
Result: FAIL
end: 21:24:33
removed posix compliance directories
1
Total 1 tests were successful


=================
GNFS Volume Mount
=================

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 3)
  Failed tests:  77, 84, 88
Files=185, Tests=1962, 93 wallclock secs ( 0.80 usr  0.39 sys +  9.33 cusr 12.81 csys = 23.33 CPU)
Result: FAIL
end: 21:31:50
removed posix compliance directories
1
Total 1 tests were successful



=================
GNFS Subdir Mount
=================

Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 3)
  Failed tests:  77, 84, 88
Files=185, Tests=1962, 92 wallclock secs ( 0.86 usr  0.40 sys +  9.38 cusr 13.10 csys = 23.74 CPU)
Result: FAIL
end: 21:35:41
removed posix compliance directories
1
Total 1 tests were successful

Comment 4 Amar Tumballi 2017-10-23 19:31:03 UTC
https://review.gluster.org/18558

Comment 7 Amar Tumballi 2017-10-30 10:08:53 UTC
https://code.engineering.redhat.com/gerrit/121726

Comment 9 Manisha Saini 2017-11-02 04:41:32 UTC
Verified this with glusterfs-3.8.4-51.el7rhgs.x86_64


Test Summary Report
-------------------
/opt/qa/tools/posix-testsuite/tests/chown/00.t   (Wstat: 0 Tests: 171 Failed: 6)
  Failed tests:  84, 88, 141, 145, 149, 153
Files=185, Tests=1962, 96 wallclock secs ( 0.73 usr  0.32 sys +  9.41 cusr 12.48 csys = 22.94 CPU)
Result: FAIL
end: 10:08:05
removed posix compliance directories
1
Total 1 tests were successful
Switching over to the previous working directory
Removing /mnt/posix_sub/run28989/


Rename test pass with this build o fuse sub-dir.Hence moving this bug to verified state.

Comment 12 errata-xmlrpc 2017-11-29 03:31:38 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://access.redhat.com/errata/RHBA-2017:3276


Note You need to log in before you can comment on or make changes to this bug.