Bug 1339527

Summary:	Heketi-cli: Error handling
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Neha <nerawat>
Component:	heketi	Assignee:	Humble Chirammal <hchiramm>
Status:	CLOSED ERRATA	QA Contact:	Neha <nerawat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	lpabon, mliyazud, pprakash, rcyriac, sashinde
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS Container Converged 1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 04:50:44 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:	1332128

Description Neha 2016-05-25 09:09:22 UTC

Description of problem:

Currently Heketi-cli doesn't provide proper error messages for most of the options

For example

heketi-cli volume create --name=testvol --size=10 --durability="replicate" --replica=2
Error: Process exited with: 1. Reason was: ()

Heketi-logs:

Err[Process exited with: 1. Reason was: ()]: Stdout []: Stderr [volume create: testvol: failed: Volume testvol already exists
]


Upstream issue:
https://github.com/heketi/heketi/issues/327

Comment 4 Luis Pabón 2016-06-06 20:33:14 UTC

Solved in Heketi 2.0.0+

Comment 5 Neha 2016-06-09 11:54:10 UTC

# heketi-cli volume create --size=10
Error: Unable to execute command on glusterfs-glusterfs-2-1-dbksi: volume create: vol_62726d510ad0a4582381c59f658b9943: failed: Host 10.70.42.182 not connected


# heketi-cli volume create --size=10
Error: Unable to execute command on glusterfs-glusterfs-1-1-k2c7y: 

# heketi-cli volume create --size=10
Error: Unable to execute command on glusterfs-glusterfs-1-1-k2c7y: volume create: vol_04c2c93ed88c7521b30614663637f990: failed: Staging failed on 10.70.43.237. Error: Brick: 10.70.43.237:/var/lib/heketi/mounts/vg_7eb7e823b1d2fad6ef11e6fe32688f99/brick_0928b1105462723c467d8e47578bd88b/brick not available. Brick may be containing or be contained by an existing brick

Verified with few scenarios when node/service is not up. Moving it to verified.

Comment 7 errata-xmlrpc 2016-08-04 04:50:44 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://rhn.redhat.com/errata/RHBA-2016-1498.html