Bug 1292773

Summary:	(RHEL6) S30Samba scripts do not work on systemd systems
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Michael Adam <madam>
Component:	samba	Assignee:	Michael Adam <madam>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	bmohanra, nlevinki, rcyriac, rhs-bugs, rjoseph, rtalur, sbhaloth, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	RHGS 3.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.5-13	Doc Type:	Bug Fix
Doc Text:	Previously, the Samba hook scripts were explicitly calling SysV-init scripts for Samba /etc/init.d/smb. Due to this, the scripts did not work as expected on systemd systems and failed to restart or reload Samba when required. With this fix, the scripts now use the service command which works both on SysV and systemd systems.	Story Points:	---
Clone Of:	1292762	Environment:
Last Closed:	2016-03-01 06:04:35 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:	1290604, 1292755, 1292762
Bug Blocks:

Comment 2 Michael Adam 2015-12-18 10:15:12 UTC

cloned for RHEL6 to stay consistent.
(Strictly needed only for RHEL7).

Comment 4 rjoseph 2015-12-19 05:23:22 UTC

Upstream Master: http://review.gluster.org/12945 
Upstream Release 3.7: http://review.gluster.org/13000
Downstream : https://code.engineering.redhat.com/gerrit/#/c/64209/

Comment 6 surabhi 2015-12-29 11:14:07 UTC

Please add fixed in version.

Comment 7 Vivek Das 2015-12-30 11:26:45 UTC

Ran this test and verified hook-scripts fix S30Samba scripts on systemd systems (RHEL6).
Did a service smb condrestart and it does start the smb service successfully.

Versions:
glusterfs-cli-3.7.5-13.el7rhgs.x86_64
samba-client-4.2.4-12.el7rhgs.x86_64

Comment 9 errata-xmlrpc 2016-03-01 06:04:35 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.

https://rhn.redhat.com/errata/RHBA-2016-0193.html