Bug 1282837 - gluster vol set <volname> ganesha.enable errors out
gluster vol set <volname> ganesha.enable errors out
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: ganesha-nfs (Show other bugs)
3.7.6
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Kaleb KEITHLEY
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-17 10:14 EST by ghatty
Modified: 2017-03-08 05:47 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-08 05:47:55 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ghatty 2015-11-17 10:14:05 EST
Description of problem:

Kaleb Keithley on glusterfs community suggested that I file this bug.

I am running into the following error when trying to enable ganesha on my system. This seems to be the same message as the one here: https://bugzilla.redhat.com/show_bug.cgi?id=1004332. 


[root@conv-gls002 ~]#  gluster volume set gvol0 ganesha.enable on
volume set: failed: Staging failed on gluster1. Error: One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again

However, I can execute some of the other gluster vol set commands.

Here is the log:
[2015-11-17 13:51:48.629507] E [MSGID: 106289] [glusterd-syncop.c:1871:gd_sync_task_begin] 0-management: Failed to build payload for operation 'Volume Set'
[2015-11-17 13:51:56.698145] E [MSGID: 106022] [glusterd-utils.c:10154:glusterd_check_client_op_version_support] 0-management: One or more clients don't support the required op-version
[2015-11-17 13:51:56.698193] E [MSGID: 106301] [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of operation 'Volume Set' failed on localhost : One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again
[2015-11-17 13:54:32.759969] E [MSGID: 106022] [glusterd-utils.c:10154:glusterd_check_client_op_version_support] 0-management: One or more clients don't support the required op-version
[2015-11-17 13:54:32.760017] E [MSGID: 106301] [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of operation 'Volume Set' failed on localhost : One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again
[2015-11-17 13:55:15.930722] E [MSGID: 106022] [glusterd-utils.c:10154:glusterd_check_client_op_version_support] 0-management: One or more clients don't support the required op-version
[2015-11-17 13:55:15.930733] E [MSGID: 106301] [glusterd-syncop.c:1274:gd_stage_op_phase] 0-management: Staging of operation 'Volume Set' failed on localhost : One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again


The work around seems to upgrade the "clients" to a certain level or disconnect them. I am running in a HA mode, and have two glusterfs nodes. Both have gluster at the same level. (3.7.6). There are no lingering mounts, as far as I can tell.

Version-Release number of selected component (if applicable):

[root@conv-gls001 glusterfs]# gluster --version
glusterfs 3.7.6 built on Nov  9 2015 15:20:26
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.

[root@conv-gls002 glusterfs]# gluster --version
glusterfs 3.7.6 built on Nov  9 2015 15:20:26
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.

Steps to Reproduce:
1.Install glusterfs 3.7.6 on two machines.
2.Install ganesha and Enable HA 
3. create a volume - say gvol0
3. run gluster vol set gvol0 nfs.disable ON

Actual results:
The gluster vol set to enable ganesha should return success.

Expected results:
volume set: failed: One or more connected clients cannot support the feature being set. These clients need to be upgraded or disconnected before running this command again


Additional info:
Comment 1 ghatty 2015-11-17 11:07:33 EST
Additional info:

I have seen this with non-HA Ganesha configuration also.
Comment 2 Kaushal 2017-03-08 05:47:55 EST
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

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