Bug 1292254
Summary: | hook script for CTDB should not change Samba config | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Michael Adam <madam> | |
Component: | scripts | Assignee: | Michael Adam <madam> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.7.6 | CC: | bugs, hgowtham | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.7 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1290151 | |||
: | 1292605 (view as bug list) | Environment: | ||
Last Closed: | 2016-04-19 07:51:02 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: | 1290151 | |||
Bug Blocks: | 1292605, 1292751 |
Description
Michael Adam
2015-12-16 20:34:00 UTC
REVIEW: http://review.gluster.org/12986 (hook-scripts: don't let ctdb script change samba config) posted (#1) for review on release-3.7 by Michael Adam (obnox) COMMIT: http://review.gluster.org/12986 committed in release-3.7 by Raghavendra Talur (rtalur) ------ commit f4357fdaca9175438f1168fcd07dd963eae4c4e2 Author: Michael Adam <obnox> Date: Wed Dec 9 18:57:59 2015 +0100 hook-scripts: don't let ctdb script change samba config There are several reasons why the behaviour in the hook scripts was bad: 1. A samba installation is clustered or non-clustered. That does not change because of the availability of the CTDB lock-volume. If the lock-volume is not available (and hence CTDB is not available or not healthy), then Samba won't be operational. But turning it into a non-clustered Samba-installation can in the worst case lead to data corruption if clients manage to access the same files (on share volumes). Hence 'clustering = yes/no' in Samba's config should not be touched. In particular, Samba should not be stopped/started by the hook script. If needed, then ctdb will take care of it. 2. Changing the idmap configuration is potentially dangerous as well. In particular the used tdb2 backend is legacy nowadays and should not be used any more in new installs. (I stems from the times when ctdb could not host persistent databases.) Changing the idmap can result in loss of access to files or in giving access to files where it is not intended. 3. The pattern used for detecting need for change is fragile. It may or may not play well possible manual changes to smb.conf. This change removes the parts that change the smb.conf file and start or stop Samba from the S29CTDB* hook scripts. > Change-Id: I72f7aabafa8f089da4531fca2572a72c22825bcc > BUG: 1290151 > Signed-off-by: Michael Adam <obnox> > Reviewed-on: http://review.gluster.org/12930 > Tested-by: Gluster Build System <jenkins.com> > Reviewed-by: Raghavendra Talur <rtalur> (cherry picked from commit 27c16d6da82876a689dfba53b8d45c3a3a657954) Change-Id: Ie1f787cebb5f6da1a658f7dead879fa854901ef5 BUG: 1292254 Signed-off-by: Michael Adam <obnox> Reviewed-on: http://review.gluster.org/12986 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Talur <rtalur> 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.7.7, please open a new bug report. glusterfs-3.7.7 has been announced on the Gluster mailinglists [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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |