Bug 1105123 - NEW - smb process starts, when user.smb option is set to disable.
Summary: NEW - smb process starts, when user.smb option is set to disable.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: gluster-smb
Version: pre-release
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Raghavendra Talur
QA Contact:
URL:
Whiteboard:
Depends On: 1104574
Blocks: 1099334
TreeView+ depends on / blocked
 
Reported: 2014-06-05 12:44 UTC by Raghavendra Talur
Modified: 2014-11-11 08:34 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1104574
Environment:
Last Closed: 2014-11-11 08:34:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-06-05 13:03:54 UTC
REVIEW: http://review.gluster.org/7994 (extras/hookscripts: When set option disables smb, don't start smb.) posted (#1) for review on master by Raghavendra Talur (rtalur)

Comment 2 Anand Avati 2014-06-10 05:53:47 UTC
REVIEW: http://review.gluster.org/7994 (extras/hookscripts: When set option disables smb, don't start smb.) posted (#2) for review on master by Raghavendra Talur (rtalur)

Comment 3 Anand Avati 2014-06-12 10:57:27 UTC
COMMIT: http://review.gluster.org/7994 committed in master by Vijay Bellur (vbellur) 
------
commit 8a2454d4490abb4860fa9ebc83c8bda8ed8aa260
Author: Raghavendra Talur <rtalur>
Date:   Thu Jun 5 18:24:56 2014 +0530

    extras/hookscripts: When set option disables smb, don't start smb.
    
    When user.smb or user.cifs option is set to disable, we remove the
    share options from smb.conf. If smb process is running, a sighup is
    required but we should not start the process if its not running.
    
    Change-Id: I1e2163ff209ba858380f7da459ff1dba3cf673f2
    BUG: 1105123
    Signed-off-by: Raghavendra Talur <rtalur>
    Reviewed-on: http://review.gluster.org/7994
    Reviewed-by: Poornima G <pgurusid>
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: Vijay Bellur <vbellur>

Comment 4 Niels de Vos 2014-09-22 12:42:12 UTC
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/

Comment 5 Niels de Vos 2014-11-11 08:34:26 UTC
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


Note You need to log in before you can comment on or make changes to this bug.