Bug 1454672

Summary: error message needs to be better when tcmu-runner is not running and gluster-block cmd is executed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Pranith Kumar K <pkarampu>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: surabhi <sbhaloth>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: rhs-bugs
Target Milestone: ---   
Target Release: RHGS 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-1.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-21 04:19:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1417151    

Description Pranith Kumar K 2017-05-23 09:43:09 UTC 
Description of problem:
When we execute:
gluster-block create r3/1 ha 3 192.168.122.61,192.168.122.123,192.168.122.113 1GiB

It gives the error:
Looks like targetcli and tcmu-runner are not installed on few nodes.

We should also include the possibility of tcmu-runner not running in the output. This is not a severe bug but it improves usability.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Prasanna Kumar Kalever 2017-05-24 09:51:57 UTC 
Patch:
https://review.gluster.org/#/c/17382/
Comment 6 surabhi 2017-06-28 14:17:18 UTC 
When we stop tcmu-runner service and execute gluster-block create command, it fails with the error as Connection failed. Please check if gluster-block daemon is operational.

The error message is proper to understand that services are not running to proceed with creation of gluster-block.

Marking the BZ to Verified.

gluster-block-0.2.1-3.el7rhgs.x86_64
Comment 8 errata-xmlrpc 2017-09-21 04:19:33 UTC 
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