Provide version-Release number of selected component (if applicable): --------------------------------------------------------------------- glusterfs-6.0-51.el7rhgs.x86_64 glusterfs-geo-replication-6.0-51.el7rhgs.x86_64 Describe the issue: ------------------- When changing the value for the config option ignore-deletes using 0 and 1 as inputs, the command succeeds but the values do not change. Also, when setting the option to true, the user must get a prompt as mentioned in Bug 1224906. # gluster volume geo-replication master-testvol 10.70.46.35::testvol config ignore-deletes 1 geo-replication config updated successfully # gluster volume geo-replication master-testvol 10.70.46.35::testvol config ignore-deletes false # gluster volume geo-replication master-testvol 10.70.46.35::testvol config ignore-deletes 0 geo-replication config updated successfully # gluster volume geo-replication master-testvol 10.70.46.35::testvol config ignore-deletes false Is this issue reproducible? If yes, share more details.: -------------------------------------------------------- Always. Steps to Reproduce: ------------------- 1. Change the config option value for ignore-deletes geo-rep option # gluster volume geo-replication master-testvol 10.70.46.35::testvol config ignore-deletes 1 Actual results: --------------- Config options do not change and there is no prompt to the user regarding the ~15 second delay. Expected results: ----------------- Config options must take 0 and 1 as inputs and the option must change appropriately. The user must also be prompted while setting the option to 1. Mandatory Information for all Bugs: ----------------------------------- # gluster v info master-testvol Volume Name: master-testvol Type: Distributed-Replicate Volume ID: b9a097c1-d596-42e9-8861-b861be510110 Status: Started Snapshot Count: 0 Number of Bricks: 2 x (2 + 1) = 6 Transport-type: tcp Bricks: Brick1: 10.70.47.71:/bricks/brick0/master-testvol-b0 Brick2: 10.70.46.208:/bricks/brick0/master-testvol-b1 Brick3: 10.70.46.92:/bricks/brick0/master-testvol-b2 (arbiter) Brick4: 10.70.46.51:/bricks/brick0/master-testvol-b3 Brick5: 10.70.47.34:/bricks/brick0/master-testvol-b4 Brick6: 10.70.46.230:/bricks/brick0/master-testvol-b5 (arbiter) Options Reconfigured: changelog.changelog: on geo-replication.ignore-pid-check: on geo-replication.indexing: on cluster.granular-entry-heal: on storage.fips-mode-rchecksum: on transport.address-family: inet nfs.disable: on performance.client-io-threads: off cluster.enable-shared-storage: enable # gluster v heal master-testvol info Brick 10.70.47.71:/bricks/brick0/master-testvol-b0 Status: Connected Number of entries: 0 Brick 10.70.46.208:/bricks/brick0/master-testvol-b1 Status: Connected Number of entries: 0 Brick 10.70.46.92:/bricks/brick0/master-testvol-b2 Status: Connected Number of entries: 0 Brick 10.70.46.51:/bricks/brick0/master-testvol-b3 Status: Connected Number of entries: 0 Brick 10.70.47.34:/bricks/brick0/master-testvol-b4 Status: Connected Number of entries: 0 Brick 10.70.46.230:/bricks/brick0/master-testvol-b5 Status: Connected Number of entries: 0 # gluster v info master-testvol Volume Name: master-testvol Type: Distributed-Replicate Volume ID: b9a097c1-d596-42e9-8861-b861be510110 Status: Started Snapshot Count: 0 Number of Bricks: 2 x (2 + 1) = 6 Transport-type: tcp Bricks: Brick1: 10.70.47.71:/bricks/brick0/master-testvol-b0 Brick2: 10.70.46.208:/bricks/brick0/master-testvol-b1 Brick3: 10.70.46.92:/bricks/brick0/master-testvol-b2 (arbiter) Brick4: 10.70.46.51:/bricks/brick0/master-testvol-b3 Brick5: 10.70.47.34:/bricks/brick0/master-testvol-b4 Brick6: 10.70.46.230:/bricks/brick0/master-testvol-b5 (arbiter) Options Reconfigured: changelog.changelog: on geo-replication.ignore-pid-check: on geo-replication.indexing: on cluster.granular-entry-heal: on storage.fips-mode-rchecksum: on transport.address-family: inet nfs.disable: on performance.client-io-threads: off cluster.enable-shared-storage: enable Additional info: