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:
Please attach engine and vdsm logs
Created attachment 661488 [details] engine logs
Created attachment 661491 [details] vdsm logs from server 1
Created attachment 661492 [details] vdsm logs from server 2
CHANGE: http://review.gluster.org/4367 (glusterd: Don't persist enable-pump in volinfo->dict) merged in master by Anand Avati (avati)
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.
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