+++ This bug was initially created as a clone of Bug #1004803 +++ Description of problem: cluster.nufa :- User should be able to set this option only for DHT volume (distributed or distributed-replicated or any other combination having distributed) Version-Release number of selected component (if applicable): 3.4.0.30rhs-2.el6_4.x86_64 How reproducible: always Steps to Reproduce: [root@DHT3 ~]# gluster volume set rep cluster.nufa on volume set: success [root@DHT3 ~]# gluster v info rep Volume Name: rep Type: Replicate Volume ID: 3c98350a-4d50-4fb5-a658-61fca078b4d0 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 10.70.37.195:/rhs/brick2/r3 Brick2: 10.70.37.66:/rhs/brick2/r3 Options Reconfigured: cluster.nufa: on Actual results: able to set nufa option on replicated volume Expected results: User should not be able to set this option for replicated volume Additional info: --- Additional comment from Scott Haines on 2013-09-27 13:08:06 EDT --- Targeting for 3.0.0 (Denali) release. --- Additional comment from Vivek Agarwal on 2014-04-07 07:41:08 EDT --- Per bug triage, between dev, PM and QA, moving these out of denali --- Additional comment from Nagaprasad Sathyanarayana on 2014-05-06 06:35:07 EDT --- BZs not targeted for Denali.
REVIEW: http://review.gluster.org/10604 (dht: removing cluster.nufa set option for replicate volumes) posted (#1) for review on master by Sakshi Bansal (sabansal)
REVIEW: http://review.gluster.org/10604 (dht: Removing cluster.nufa set option for volumes not having distributed) posted (#2) for review on master by Sakshi Bansal (sabansal)
REVIEW: http://review.gluster.org/10604 (dht: Removing cluster.nufa set option for volumes not having distributed) posted (#3) for review on master by Sakshi Bansal (sabansal)
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions