Red Hat Bugzilla – Bug 1315170
Wrong interpretation of disk size in gverify.sh script
Last modified: 2016-03-07 01:56:22 EST
+++ This bug was initially created as a clone of Bug #1305839 +++
Description of problem:
Run gverify script as below:
#/usr/local/libexec/glusterfs/gverify.sh tv1 root gfvm4 tv2 22 /tmp/test.log
/usr/local/libexec/glusterfs/gverify.sh: line 206: [: 1-blocks: integer expression expected
Version-Release number of selected component (if applicable):
This bug is not easily reproducible, as it is not returning any error.
If the script is executed standalone, then only it can be reproduced.
Steps to Reproduce:
1. Setup geo-replication
2. Run gverify script
Throws error "integer expression expected"
Should not throw any error.
returns 0 for success, can be verified as echo $? after executing the script.
--- Additional comment from Vijay Bellur on 2016-02-09 06:33:10 EST ---
REVIEW: http://review.gluster.org/13407 (geo-rep: Fix invalid disk size in gverify.sh) posted (#2) for review on master by Saravanakumar Arumugam (firstname.lastname@example.org)
--- Additional comment from Vijay Bellur on 2016-03-01 02:57:24 EST ---
COMMIT: http://review.gluster.org/13407 committed in master by Jeff Darcy (email@example.com)
Author: Saravanakumar Arumugam <firstname.lastname@example.org>
Date: Tue Feb 9 16:44:03 2016 +0530
geo-rep: Fix invalid disk size in gverify.sh
Due to the wrong interpretation of disk size, gverify.sh script
exits in between with error "integer expression expected".
This error can be observed, only if gverify.sh is run standalone.
Fix the interpretation of disk size.
Also, verify that master and slave's gluster version are same.
Signed-off-by: Saravanakumar Arumugam <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Aravinda VK <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
Reviewed-by: Kotresh HR <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
not applicable in 3.7, so closing the bug.