+++ 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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- 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 (amukherj) --- 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 (amukherj) ------ commit fd16186b403e38763b1d0b39c8c7ce14ffc508ba Author: Atin Mukherjee <amukherj> Date: Wed Aug 5 16:02:49 2015 +0530 glusterd: improve error logs for unsupported clients Change-Id: I90be46a7b25cc3efd0e61c9a145852e9027f5f64 BUG: 1302205 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/11831 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Prashanth Pai <ppai> Reviewed-by: Kaushal M <kaushal> NetBSD-regression: NetBSD Build System <jenkins.org>
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. https://access.redhat.com/errata/RHBA-2016:1240