+++ This bug was initially created as a clone of Bug #1084958 +++ Description of problem: ========================================= Tried the following workaround to install glusterfs-server: mkdir -p /var/lib/glusterd/hooks/1/{start,stop,add-brick,set}/{pre,post} running that before yum install glusterfs-server Once the gluster packages are installed, mount of gluster volume via SMB is failing. Version-Release number of selected component (if applicable): glusterfs-server-3.5qa2-0.304.git0c1d78f.el6rhs.x86_64 How reproducible: Tried cifs mount several times. Steps to Reproduce: 1.Install the latest glusterfs rpm's 2.Mount the volume via cifs Actual results: The mount of gluster volume via SMB fails. Expected results: The SMB mount should happen successfully. Additional info:
REVIEW: http://review.gluster.org/7409 (gfapi: In glfs_set_volfile_server() remove the port number check.) posted (#1) for review on master by Poornima G (pgurusid)
COMMIT: http://review.gluster.org/7409 committed in master by Vijay Bellur (vbellur) ------ commit 6567d141c1b0112acb35e711371ae5a879fc645a Author: Poornima G <pgurusid> Date: Mon Apr 7 17:38:32 2014 +0530 gfapi: In glfs_set_volfile_server() remove the port number check. The documentation for glfs_set_volfile_server() api says that the port zero is a valid value. Specifying 0 uses the default port number GF_DEFAULT_BASE_PORT. Hence removing the check for port being zero. Change-Id: I942a7fe54a418231a438ab67756537df8f28d2de BUG: 1084964 Signed-off-by: Poornima G <pgurusid> Reviewed-on: http://review.gluster.org/7409 Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/8374 (gfapi: In glfs_set_volfile_server() remove the port number check.) posted (#1) for review on release-3.5 by Poornima G (pgurusid)
Bug 1124728 will be used for the glusterfs-3.5.x version. This bug was used for the master branch. The release-3.6 branch has been created after the change was merged, so this should have been fixed in any 3.6.x version. Please do not use closed bugs, or one bug for patches to different glusterfs versions.