+++ This bug was initially created as a clone of Bug #1161037 +++ Description of problem: In case of command gets timed out, cli doesn't throw any error message Version-Release number of selected component (if applicable): Mainline How reproducible: Everytime Steps to Reproduce: 1. Run a gluster cli command 2. Ensure it times out after 120 seconds Actual results: No message is shown Expected results: time out message should be displayed Additional info: --- Additional comment from Anand Avati on 2014-11-06 04:11:01 EST --- REVIEW: http://review.gluster.org/9017 (cli: for rpc timeout throw a time out message) posted (#6) for review on master by Atin Mukherjee (amukherj) --- Additional comment from Anand Avati on 2014-11-07 03:58:51 EST --- REVIEW: http://review.gluster.org/9017 (cli: for rpc timeout throw a time out message) posted (#7) for review on master by Atin Mukherjee (amukherj) --- Additional comment from Anand Avati on 2014-11-11 01:43:36 EST --- COMMIT: http://review.gluster.org/9017 committed in master by Kaushal M (kaushal) ------ commit b3ce1bfeaab08cdf51cccd60d6d7047c692f73a9 Author: Atin Mukherjee <amukherj> Date: Fri Oct 31 06:52:39 2014 +0530 cli: for rpc timeout throw a time out message Change-Id: I9660df1c3b2707583bd95806011b650cd1a2df1b BUG: 1161037 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/9017 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
As discussed with Scrum Team, this bug could be verified for RHS 3.0.3 timeline. Providing qa-ack
Downstream patch link : https://code.engineering.redhat.com/gerrit/36396
Verified the same with glusterfs-3.4.0.33-1.el6rhs Simulated the cli-timeout by blocking glusterd using gdb and also using iptables mechanisms Performed 2 tests, Test-1 1. In a 2 node cluster, gdb-ed in to one of the glusterd process (i.e) gdb -p `pidof glusterd` 2. From the other node in the cluster, executed 'gluster volume status' Observation: cli timedout error message was thrown Test-2 1. In a 2 node cluster, simulated network disconnection using iptables and immediately issued 'gluster volume status' command Observation: After cli timesout, corresponding error message was thrown on the console. Error messages as seen on the console --------------------------------------- [root@dhcp37-44 ~]# gluster v status Error : Request timed out [root@dhcp37-44 ~]# echo $? 1 Marking this bug as verified.
Atin, Please review the edited doc text and sign-off.
Doc text looks okay to me, verified.
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://rhn.redhat.com/errata/RHBA-2015-0038.html