Bug 1213821 - nfs-ganesha: correct the interactive query thats displayed while executing features.ganesha cmd
Summary: nfs-ganesha: correct the interactive query thats displayed while executing fe...
Keywords:
Status: CLOSED DUPLICATE of bug 1217793
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: 3.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Niels de Vos
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 11:21 UTC by Saurabh
Modified: 2016-01-19 06:15 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-29 13:27:03 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Saurabh 2015-04-21 11:21:21 UTC
Description of problem:
while executing gluster features.ganesha enable command a query is displayed on stdout, so we need to correct the spelling over there,
Enabling NFS-Ganesha requires Gluster-NFS to bedisabled across the trusted pool. Do you still want to continue? (y/n)

Version-Release number of selected component (if applicable):
glusterfs-3.7dev-0.1009.git8b987be.el6.x86_64

How reproducible:
always

Expected results:
there should be a space in between two words "be" and "disabled"

Additional info:

Comment 1 Meghana 2015-05-05 05:58:32 UTC
Changed as part of the fix, http://review.gluster.org/#/c/10283/
which is merged both on master and release-3.7

Comment 2 Meghana 2015-05-05 06:01:50 UTC
Changed as part of the fix, http://review.gluster.org/#/c/10283/
which is merged both on master and release-3.7

Comment 4 Niels de Vos 2015-10-29 13:27:03 UTC
(In reply to Meghana from comment #2)
> Changed as part of the fix, http://review.gluster.org/#/c/10283/
> which is merged both on master and release-3.7

This is a change for the master branch, bug 1217793 seems to be the backport for release-3.7.

*** This bug has been marked as a duplicate of bug 1217793 ***


Note You need to log in before you can comment on or make changes to this bug.