Bug 826465

Summary: Gluster - Backend: Unpredictable results when setting nfs.disable to on
Product: [Retired] oVirt Reporter: Daniel Paikov <dpaikov>
Component: ovirt-engine-coreAssignee: Raghavendra Bhat <rabhat>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acathrow, dyasny, hateya, iheim, mgoldboi, pprakash, shireesh, ykaul
Target Milestone: ---   
Target Release: 3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: glusterfs-3.4.0qa4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-15 06:47:50 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:
Attachments:
Description Flags
engine.log
none
vdsm.log none

Description Daniel Paikov 2012-05-30 09:24:08 UTC
Created attachment 587656 [details]
engine.log

Volumes -> select volume -> Volume Options -> nfs.disable (by default set to "off") -> Edit -> change "off" to "on" -> OK -> the result is that nfs.disable remains "off" but a new key is added with the name "nfs.enable-ino32" and with the value "on".

Comment 1 Bala.FA 2012-05-31 01:58:53 UTC
I suspect that it could be a gluster bug.
1, Can yoy send me 'gluster --version' output of the host?
2. Can you attach respective vdsm log?

Comment 2 Daniel Paikov 2012-05-31 09:31:34 UTC
Created attachment 588014 [details]
vdsm.log

Attaching vdsm.log (from a new run of the same flow).

Gluster version:
glusterfs 3.3.0qa41 built on May 16 2012 23:00:40

Comment 3 Shireesh 2012-06-11 10:16:49 UTC
This is happening because the "gluster volume set help-xml" command is not returning "nfs.disable" as one of the options. Assigning to Vijay for resolution.

Comment 4 Shireesh 2012-06-11 10:19:41 UTC
*** Bug 826942 has been marked as a duplicate of this bug. ***

Comment 5 Raghavendra Bhat 2012-12-04 10:04:23 UTC
seems to me as duplicate of bug 828027. That bug is closed as fixed with below comment:

The patch has been accepted into both master & release-3.3 branches upstream.
The respective commits are,
4b09879 (glusterd: nfs.disable fix for "volume set help") for master, reviewed
at http://review.gluster.com/3509
948b9a5 (glusterd: nfs.disable fix for "volume set help") for release-3.3,
reviewed at http://review.gluster.org/3881
----

also checked on 3.4.0qa4, and below is the output

[root@thinkpad raghu]# gluster volume set help-xml | xmllint --format - | grep nfs.disable
    <name>nfs.disable</name>