Bug 986348 - RFE: Disabled Samba becomes Enabled again after updating to RHS2.0 update 5
RFE: Disabled Samba becomes Enabled again after updating to RHS2.0 update 5
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribution (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Sayan Saha
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2013-07-19 09:47 EDT by Marcel Hergaarden
Modified: 2016-04-11 07:55 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-04-11 07:55:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marcel Hergaarden 2013-07-19 09:47:13 EDT
Description of problem:

Disabled Samba by moving S30Samba -> K30Samba 
inside: /var/lib/glusterd/hooks/1/start/post as suggested by documentation.

Version-Release number of selected component (if applicable):
RHS 2.0 update 5

How reproducible:
- Install RHS 2.0 Update 4.
- Disable automatic samba export creation by moving S30Samba script to K30Samba..
- Update RHS 2.0 to update 5 by using yum update
- Samba exports are back active again and fully writeable as Guest !!

Steps to Reproduce:
1. Install RHS2.0 update 4
2. Disable automatic samba export
3. update to RHS2.0 update 5 by using yum update
4. Automatic samba export is enabled again.

Actual results:
Automatic samba export is enabled again.

Expected results:
Samba export was disabled, should therefore remain disabled.

Additional info:
It doesn't check on existance of K30Samba....
Simply creates a new start script inside the hooks dir.
Comment 2 Marcel Hergaarden 2013-07-19 10:25:54 EDT
Eventually it could be that the same goes for other services used in hooks aswell.
i.e. not only for the samba service but also for other services as managed by hooks.
Comment 3 Alok 2016-04-11 07:55:29 EDT
The version of Red Hat Gluster Storage on which this issue was reported has reached end of life [1], hence this bug  is being closed. If the issue is still observed on a current version of Red Hat Gluster Storage, Please file a new bug  on the current version.

[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html"

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