Bug 886000

Summary: [RHSC] Option enable-pump for a volume keeps appearing and disappearing on the Console, after replace-brick operation is started on that volume from gluster CLI.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: glusterfsAssignee: krishnan parthasarathi <kparthas>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: high Docs Contact:
Priority: medium    
Version: 2.0CC: amarts, mmahoney, nsathyan, pprakash, rhs-bugs, shaines, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0qa8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 928794 (view as bug list) Environment:
Last Closed: 2013-09-23 22:34:42 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:    
Bug Blocks: 928794    
Attachments:
Description Flags
engine logs
none
vdsm logs from server 1
none
vdsm logs from server 2 none

Description Shruti Sampat 2012-12-11 09:43:38 UTC 
Description of problem:
---------------------------------------
After running "gluster volume replace-brick <vol-name> <old-brick> <new-brick> start" on a volume from gluster CLI, the Volume options sub-tab shows an entry for the option 'enable-pump' with value 1. The Events tab reports the following message - 

"Option enable-pump was reset on Volume test from gluster CLI. Now reset in engine DB as well."

Immediately after the above message is seen, the Events tab reports another message as follows and the entry 'enable-pump' disappears from the Volume Options sub-tab -  

"Option enable-pump was reset on Volume test from gluster CLI. Now reset in engine DB as well."

This sequence of setting and resetting continues to be reported on the Events tab, and the entry for 'enable-pump' keeps appearing and disappearing.

Version-Release number of selected component (if applicable):
2.1-qa18.el6ev

How reproducible:
Always

Steps to Reproduce:
1. Run 'gluster volume replace-brick start' on a volume from gluster CLI
  
Actual results:
The Events tab keeps reporting messages that volume option 'enable-pump' was set and then reset and and the Volume Options entry for 'enable-pump' keeps appearing and disappearing

Expected results:
The enable-pump option entry should remain as 1 till the replace-brick operation is either paused, aborted or committed.

Additional info:
Comment 2 Shireesh 2012-12-11 09:49:37 UTC 
Please attach engine and vdsm logs
Comment 3 Shruti Sampat 2012-12-11 14:22:15 UTC 
Created attachment 661488 [details]
engine logs
Comment 4 Shruti Sampat 2012-12-11 14:24:53 UTC 
Created attachment 661491 [details]
vdsm logs from server 1
Comment 5 Shruti Sampat 2012-12-11 14:26:27 UTC 
Created attachment 661492 [details]
vdsm logs from server 2
Comment 7 Vijay Bellur 2013-01-17 02:37:05 UTC 
CHANGE: http://review.gluster.org/4367 (glusterd: Don't persist enable-pump in volinfo->dict) merged in master by Anand Avati (avati)
Comment 8 Shruti Sampat 2013-03-19 10:04:59 UTC 
Verified as fixed in glusterfs 3.4.0qa8. Option enable-pump no longer appears in the output of "gluster volume info <vol-name>" when replace-brick operation is started on a volume.
Comment 9 Scott Haines 2013-09-23 22:34:42 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