Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: No proper return of SUCCESS or FAILURE in gluster-block [root@localhost ~]# gluster-block list blockmaster1 *Nil* [root@localhost ~]# gluster-block create blockmaster1/blockvol-b3e08d5b-3ba1-11e7-8095-c85b7636c232 ha 1 10.67.116.108 2GiB --json [root@localhost ~]# echo $? 255 [root@localhost ~]# gluster-block list blockmaster1 *Nil* [root@localhost ~]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
gluster-block (0.2) Repository rev: https://github.com/gluster/gluster-block.git Copyright (c) 2016 Red Hat, Inc. <https://redhat.com/> gluster-block comes with ABSOLUTELY NO WARRANTY. It is licensed to you under your choice of the GNU Lesser General Public License, version 3 or any later version (LGPLv3 or later), or the GNU General Public License, version 2 (GPLv2), in all cases as published by the Free Software Foundation.
https://review.gluster.org/17461
Tried multiple times, create of gluster block from various nodes, it gives success or failure after each attempt. Marking the BZ to verified. gluster-block-0.2.1-1.el7rhgs.x86_64 tcmu-runner-1.2.0-4.el7rhgs.x86_64
It was my mistake that, I failed to mention, this issue is completely reproducible when we give wrong block IPs in the command line. I know I am late to mention this, however it would be appreciated if we can verify that scenario in this bz.
As mentioned by Humble tried creating block with invalid host Ip and it takes around 240-300 secs to exit and give the message as follows: gluster-block create blockstor/goodblock ha 1 auth enable google.com 1GiB failed to configure on google.com : Connection timed out RESULT:FAIL Discussed this with Prasanna and the default wait time is 300 secs so it tries until then and then it will exit with the message.
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/RHEA-2017:2773