Bug 863907 - GlusterFS automatically starts smb service when it is disabled w/ chkconfig
Summary: GlusterFS automatically starts smb service when it is disabled w/ chkconfig
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Niels de Vos
QA Contact: Ujjwala
URL:
Whiteboard:
Depends On: 861506
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-08 03:22 UTC by Scott Haines
Modified: 2018-11-29 19:55 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.3.0.3rhs-33.el6rhs
Doc Type: Bug Fix
Doc Text:
Clone Of: 861506
Environment:
Last Closed: 2012-11-12 18:47:28 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 225093 0 None None None 2012-10-08 03:22:23 UTC
Red Hat Product Errata RHSA-2012:1456 0 normal SHIPPED_LIVE Low: Red Hat Storage 2.0 security, bug fix, and enhancement update #3 2012-11-12 23:46:48 UTC

Comment 3 Ujjwala 2012-10-18 07:28:38 UTC 
Verified the bug on 3.3.0.3rhs-33.el6rhs.x86_64 build.
Steps to verify:
case1:
1. Update RHS 2.0 to 3.3.0.3rhs-33.el6rhs.x86_64 build.
2. chkconfig smb off
3. Check the smb service is not started
4. Create a gluster volume and start the volume.
5. 'service smb status' and verify that the smb service is not started and gluster volume start does not start the smb service.
6. Check /var/log/messages and verify there are no smb related error messages.

case2:
7. execute 'service smb start' on all nodes
8. gluster volume <volname> start force
9. 'service smb status' and verify that smb is still running and the volume start does not affect smb status if it is already running.
Comment 5 errata-xmlrpc 2012-11-12 18:47:28 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/RHSA-2012-1456.html
Note You need to log in before you can comment on or make changes to this bug.