Bug 1464641 - gluster-block create prints "(null)" when tcmu-runner is not running
Summary: gluster-block create prints "(null)" when tcmu-runner is not running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Prasanna Kumar Kalever
QA Contact: Sweta Anandpara
URL:
Whiteboard: 3.3.0-devel-freeze-exception
: 1465489 (view as bug list)
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-06-24 06:48 UTC by Pranith Kumar K
Modified: 2017-09-21 04:20 UTC (History)
9 users (show)

Fixed In Version: gluster-block-0.2.1-4.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:20:54 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2773 0 normal SHIPPED_LIVE new packages: gluster-block 2017-09-21 08:16:22 UTC

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
Note You need to log in before you can comment on or make changes to this bug.