Description of problem: SATT16 and SATT17 tests failed while running pynfs test suite. Version-Release number of selected component (if applicable): nfs-ganesha-2.4.1-9.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create nfs ganesha cluster. 2. Create a volume and run pynfs test suite from client. ./testserver.py 10.70.44.137:/testvol -v --outfile ~/pynfs.run --maketree --showomit --rundep all > /tmp/pynfs-sattr.log Actual results: SATT16 and SATT17 tests are failing. Expected results: All the pynfs tests should pass. Additional info: SATT16 st_setattr.testEmptyPrincipal : FAILURE Setting empty owner should return NFS4ERR_INVAL, instead got NFS4_OK SATT17 st_setattr.testEmptyGroupPrincipal : FAILURE Setting empty owner_group should return NFS4ERR_INVAL, instead got NFS4_OK packet trace and sosreports are attached shortly.
packet trace and sosreports are at, http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1440072/
These are two new pynfs test cases. A fix will be merged into V2.5-dev-21 today.
https://github.com/nfs-ganesha/nfs-ganesha/commit/8e8f1cfbeb03423d6e25c0c8cc7cb831ff6533f6
Thanks Dan!
Verified this bug on nfs-ganesha-2.4.4-6.el7rhgs.x86_64 SATT16 and SATT17 tests are now passing with this build. SATT15 st_setattr.testChangeGranularity : PASS SATT16 st_setattr.testEmptyPrincipal : PASS SATT17 st_setattr.testEmptyGroupPrincipal : PASS SATT18 st_setattr.testMixed : PASS Hence Moving this bug to verified state
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/RHEA-2017:2779