Bug 1464641

Summary:	gluster-block create prints "(null)" when tcmu-runner is not running
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Pranith Kumar K <pkarampu>
Component:	gluster-block	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED ERRATA	QA Contact:	Sweta Anandpara <sanandpa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, kramdoss, pkarampu, prasanna.kalever, rcyriac, rhinduja, rhs-bugs, sanandpa, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	3.3.0-devel-freeze-exception
Fixed In Version:	gluster-block-0.2.1-4.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:20:54 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-06-24 06:48:15 UTC

Description of problem:
11:18:28 :( ⚡ gluster-block create d1/1-img ha 1 localhost.localdomain 10GiB
(null)
RESULT:FAIL

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


How reproducible:
Always, when tcmu-runner is not running on my machine

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
11:45:18 :( ⚡ gluster-block create d1/1-img ha 1 localhost.localdomain 10GiB
failed to configure on localhost.localdomain tcmu-runner not running
RESULT:FAIL


Additional info:

Comment 2 Pranith Kumar K 2017-06-24 06:49:11 UTC

https://review.gluster.org/17622

Comment 5 Prasanna Kumar Kalever 2017-06-28 06:49:26 UTC

*** Bug 1465489 has been marked as a duplicate of this bug. ***

Comment 10 Sweta Anandpara 2017-07-17 09:14:57 UTC

Have been testing in gluster-block-0.2.1-6 and glusterfs-3.8.4-33.
As mentioned in comment8, the code path to hit this issue is dead, and hence we will never end up in a situation as mentioned in description. 

Having said that, did execute the steps in and around the ones mentioned. Also checked for any unexpected errors in log messages- and it does not seem to be out of the ordinary.

Moving this bug to verified in 3.3.

Comment 12 errata-xmlrpc 2017-09-21 04:20:54 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