[Bugs] [Bug 1218976] New: cluster.nufa :- User should be able to set this option only for DHT volume (distributed or distributed-replicated or any other combination having distributed)

bugzilla at redhat.com bugzilla at redhat.com
Wed May 6 10:34:45 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1218976

            Bug ID: 1218976
           Summary: cluster.nufa :- User should be able to set this option
                    only for  DHT volume (distributed or
                    distributed-replicated or any other combination having
                    distributed)
           Product: GlusterFS
           Version: mainline
         Component: distribute
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: sabansal at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    mzywusko at redhat.com, nbalacha at redhat.com,
                    racpatel at redhat.com, rhs-bugs at redhat.com,
                    storage-qa-internal at redhat.com, vbellur at redhat.com



+++ 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 at DHT3 ~]# gluster volume set rep cluster.nufa on
volume set: success
[root at 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list