Bug 856997
Summary: | NFS enabling/disabling option is not intuitive | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vidya Sakar <vinaraya> |
Component: | glusterd | Assignee: | Rajesh <rajesh> |
Status: | CLOSED NOTABUG | QA Contact: | Saurabh <saujain> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0 | CC: | mzywusko, rajesh, rfortier, rhs-bugs, sdharane, shaines, vagarwal, vbellur |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-27 11:19:58 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: |
Description
Vidya Sakar
2012-09-13 10:36:52 UTC
gluster volume set <VOLNAME> nfs.disable [yes|no] is the intended option. using on/off works because of our internal interpretation of [yes|no], [on|off], [enable|disable] (an even more confusing pair for nfs.disable), [1|0] as boolean [true|false] all respectively. |