Bug 1541568
Summary: | [GSS] logic in S30samba-start.sh hook script needs tweaking | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Pan Ousley <pousley> | |
Component: | samba | Assignee: | Anoop C S <anoopcs> | |
Status: | CLOSED ERRATA | QA Contact: | Vivek Das <vdas> | |
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | rhgs-3.3 | CC: | amukherj, anoopcs, atoborek, atumball, bkunal, gdeschner, rhs-bugs, rhs-smb, sankarshan, sheggodu, srmukher, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Reopened, ZStream | |
Target Release: | RHGS 3.4.z Batch Update 3 | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.2-33 | Doc Type: | Enhancement | |
Doc Text: |
With this release, the Samba hook script has been improved for adding volume share section in the smb.conf file. To export gluster volume as SMB share via Samba, one of the following volume options, user.cifs or user.smb is required. The existing glusterfs volume share sections in smb.conf will remain unchanged.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1575836 (view as bug list) | Environment: | ||
Last Closed: | 2019-02-04 07:41:25 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1575836 | |||
Bug Blocks: |
Description
Pan Ousley
2018-02-02 22:21:03 UTC
Sorry, closed the wrong bug. Following required patches landed in upstream: * https://review.gluster.org/c/glusterfs/+/19204 * https://review.gluster.org/c/glusterfs/+/21124 Newly created GlusterFS volumes are not exported as SMB share via Samba unless either of 'user.cifs' or 'user.smb' volume set options are enabled on the volume. The above is validated and is working as expected in glusterfs-3.12.2-34. 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/RHBA-2019:0263 |