Description of problem: ********************************* After upgrading the systems to latest samba and gluster builds the samba shares are not accessible from windows client and linux cifs client. Version-Release number of selected component (if applicable): samba-4.2.4-11.el7rhgs.x86_64 glusterfs-3.7.5-13.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1.Upgrade the setups from previous version of samba and gluster 2.Mount the volume via cifs client or access the share from windows client 3. Actual results: Mount /access share on windows and Linux cifs client fails. Expected results: Mount of volume / access to samba share should succeed. Additional info:
Upstream patch exists. It is tested in downstream with scratch build https://brewweb.devel.redhat.com/taskinfo?taskID=10272563 from branch private-obnox-rhgs-3.1-rhel-6. Patch is reviewed upstream and on its way to master upstream. Will continue with upstream release branches in upstream BZ and final downstream packaging.
Updated the build on both RHEL6 and RHEL7 : 1.Executed mount from Linux cifs client and accessed the share , mount successfull. 2. Accessed the samba share from Windows client, and the access is successfull. 3. Tried with AD User on a CTDB VIP, the access to share is successfull. Currently running sanity on both the systems.Will update the BZ soon with the results.
The sanity passed on both RHEL6 and RHEL7 with the latest builds as follows : RHEL6 : samba-4.2.4-12.el6rhs.x86_64.rpm RHEL7 : samba-4.2.4-12.el7rhgs.x86_64.rpm Mount of Volume is successfull on cifs client. Access to the samba share from windows client is successfull. Ran Basic I/O 's (Create dirs,files,deep dirs,renames,deletes on Linux cifs client and windows share)successfull. Also verified with subdirectory mounts and I/O's on the same. Marking the BZ verified.
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://rhn.redhat.com/errata/RHBA-2016-0326.html