+++ This bug was initially created as a clone of Bug #1302205 +++
Description of problem:
When a volume set is executed and if there are already connected clients which are incompatible w.r.t op-version the error message doesn't point out which first client needs to be upgraded first.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Vijay Bellur on 2016-01-27 02:13:36 EST ---
REVIEW: http://review.gluster.org/11831 (glusterd: improve error logs for unsupported clients) posted (#5) for review on master by Atin Mukherjee (email@example.com)
--- Additional comment from Vijay Bellur on 2016-01-27 22:50:53 EST ---
COMMIT: http://review.gluster.org/11831 committed in master by Atin Mukherjee (firstname.lastname@example.org)
Author: Atin Mukherjee <email@example.com>
Date: Wed Aug 5 16:02:49 2015 +0530
glusterd: improve error logs for unsupported clients
Signed-off-by: Atin Mukherjee <firstname.lastname@example.org>
Reviewed-by: Pranith Kumar Karampuri <email@example.com>
Tested-by: Pranith Kumar Karampuri <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Prashanth Pai <email@example.com>
Reviewed-by: Kaushal M <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
The fix is now available in rhgs-3.1.3 branch, hence moving the state to Modified.
Verified this bug using the build "glusterfs-3.7.9-1"
Fix is working properly, when volume is mounted on unsupported clients and volume set was done, it will through error message saying which client need to be update first.
#gluster volume set Dis performance.readdir-ahead off
volume set: failed: One of the client 10.70.37.76:1023 is running with op-version 30703 and doesn't support the required op-version 30707. This client needs to be upgraded or disconnected before running this command again
with this details, moving bug to next state.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.