+++ This bug was initially created as a clone of Bug #1386702 +++ Description of problem: During Bakeathon, steved reported that there are below failures in cthon general tests when ACLs are enabled on FSAL_GLUSTER share. >>>>>>>>>> ./server -g -o tcp,v3,sec=sys -m /mnt/nfsv3tcp -p /bakeathon/rhel7/nfsv3tcp redhat-117 ./server -g -o proto=tcp,sec=sys,v4 -m /mnt/nfsv4tcp -p /bakeathon/rhel7/nfsv4tcp redhat-117 ./server -g -o proto=tcp,sec=sys,v4.1 -m /mnt/nfsv41tcp -p /bakeathon/rhel7/nfsv41tcp redhat-117 ./server -g -o proto=tcp,sec=sys,v4.2 -m /mnt/nfsv42tcp -p /bakeathon/rhel7/nfsv42tcp redhat-117 Four simultaneous large compiles /usr/bin/time: cannot run ./large4.sh: Permission denied 0.00user 0.00system 0:00.00elapsed 0%CPU (0avgtext+0avgdata 336maxresident)k 0inputs+8outputs (0major+70minor)pagefaults Waiting for 'g' to finish... The '-g' test using '-o tcp,v3,sec=sys' args to redhat-117: Failed!! The '-g' test using '-o proto=tcp,sec=sys,v4' args to redhat-117: Failed!! The '-g' test using '-o proto=tcp,sec=sys,v4.2' args to redhat-117: Failed!! The '-g' test using '-o proto=tcp,sec=sys,v4.1' args to redhat-117: Failed!! Done: 04:10:53 PM ./server -s -o tcp,v3,sec=sys -m /mnt/nfsv3tcp -p /bakeathon/rhel7/nfsv3tcp redhat-117 ./server -s -o proto=tcp,sec=sys,v4 -m /mnt/nfsv4tcp -p /bakeathon/rhel7/nfsv4tcp redhat-117 check for proper open/unlink operation runtests.wrk: line 24: ./op_unlk: Permission denied special tests failed Tests failed, leaving /mnt/nfsv3tcp mounted ./server -s -o proto=tcp,sec=sys,v4.1 -m /mnt/nfsv41tcp -p /bakeathon/rhel7/nfsv41tcp redhat-117 ./server -s -o proto=tcp,sec=sys,v4.2 -m /mnt/nfsv42tcp -p /bakeathon/rhel7/nfsv42tcp redhat-117 Waiting for 's' to finish... The '-s' test using '-o tcp,v3,sec=sys' args to redhat-117: Failed!! The '-s' test using '-o proto=tcp,sec=sys,v4' args to redhat-117: Failed!! Done: 04:11:02 PM <<<<<<<<<<<<<< Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 1386699 ***