Bug 1244670 - After executing volume set command hook script takes a while to run and update the share information in smb.conf
Summary: After executing volume set command hook script takes a while to run and updat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Anoop
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-20 09:02 UTC by surabhi
Modified: 2018-02-06 06:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-06 06:13:57 UTC
Embargoed:


Attachments (Terms of Use)

Description surabhi 2015-07-20 09:02:18 UTC
Description of problem:

After setting the volume option user.cifs/user.smb to enable or disable , the hook scripts are getting executed with some delay(few seconds) and the share entry from smb.conf gets removed or added with the delay and not immediately as we set the option.

In previous releases , the smb.conf used to get updated as soon as we execute the command gluster volume set.

Already verified that once the hook script gets the instruction, it executes the command within 1 sec, the delay is between executing teh vol set command and execution of hook script.


Version-Release number of selected component (if applicable):
glusterfs-3.7.1-9.el7rhgs.x86_64


How reproducible:
Always

Steps to Reproduce:
1.create a volume
2.start, do volume set 
3. check testparm/smb.conf for the share entry immediately after executing command

Actual results:
it takes few seconds delay to execute hook script after executing vol set.

Expected results:
as per pre


Additional info:

Comment 2 surabhi 2015-07-20 09:04:25 UTC
Expected results:
as per previous releases as soon as volume set command is executed , the hook scripts gets executed and share entry gets updated for smb.conf.


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