Description of problem: Renaming a directory into existing file should return NFS4ERR_EXIST or NFS4ERR_EXIST, instead we get NFS4ERR_ISDIR in one of the pynfs tests. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Export a volume using nfs-ganesha. 2.Mount the volume in nfsv4 on a client. 3.Run the specific pynfs test by using the following command,/testserver.py -v --outfile ~/pynfs.run.1 --maketree 10.70.43.168:/testvol --showomit --rundeps RNM12 Actual results: RNM12 st_rename.testDirToObj : FAILURE RENAME dir into existing file should return NFS4ERR_EXIST or NFS4ERR_NOTDIR, instead got NFS4ERR_ISDIR Expected results: It should pass. Additional info:
REVIEW: http://review.gluster.org/7226 (Changing the errno in glfs_h_rename) posted (#1) for review on master by Meghana M (mmadhusu)
COMMIT: http://review.gluster.org/7226 committed in master by Anand Avati (avati) ------ commit 79d2a9e5b83b4d773e5b821c5c55f24718745cb7 Author: Meghana <mmadhusu> Date: Tue Mar 11 14:52:34 2014 +0000 Changing the errno in glfs_h_rename Change-Id: I006215d910ee854aee488f3880f39ed425f294cc BUG: 1075488 Reviewed-on: http://review.gluster.org/7226 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users