Bug 999921

Summary:	Hook scripts for samba don't add default log file and log level in smb.conf
Product:	Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	samba	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	surabhi <sbhaloth>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	gluster-bugs, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.23rhs-1.el6rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	999910	Environment:
Last Closed:	2013-09-23 22:32:16 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:
Bug Depends On:	999910
Bug Blocks:

Description Raghavendra Talur 2013-08-22 11:24:45 UTC

+++ This bug was initially created as a clone of Bug #999910 +++

Description of problem:
Hook scripts for samba add entry in smb.conf for each volume.
However, they don't add default log file for the plugin.
In case of errors, this will lead to having no record of what went wrong
in the client process stack.


How reproducible:
Always

--- Additional comment from Anand Avati on 2013-08-22 07:17:43 EDT ---

REVIEW: http://review.gluster.org/5685 (extras/hookscripts: Add default logfile for glusterfs vfs plugin.) posted (#1) for review on master by Raghavendra Talur (rtalur)

Comment 2 Raghavendra Talur 2013-08-22 11:52:42 UTC

posted patch for review at https://code.engineering.redhat.com/gerrit/#/c/11779/

Comment 3 surabhi 2013-09-04 13:53:51 UTC

Verified the bug with latest version:
samba-glusterfs-3.6.9-160.3.el6rhs.x86_64
glusterfs-3.4.0.30rhs-2.el6rhs.x86_64

Now the new shares have default log file and log level set.

Comment 4 Scott Haines 2013-09-23 22:32:16 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-1262.html