Bug 1228601

Summary:	[Virt-RHGS] Creating a image on gluster volume using qemu-img + gfapi throws error messages related to rpc_transport
Product:	[Community] GlusterFS	Reporter:	krishnan parthasarathi <kparthas>
Component:	rpc	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	amukherj, bugs, gluster-bugs, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1227583	Environment:	virt RHGS Integration
Last Closed:	2015-06-20 09:50:08 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:	1222785, 1227583
Bug Blocks:

Description krishnan parthasarathi 2015-06-05 10:11:13 UTC

+++ This bug was initially created as a clone of Bug #1227583 +++

+++ This bug was initially created as a clone of Bug #1222785 +++

Description of problem:
-----------------------
While creating VM Image file using qemu-img ( which uses qemu's native driver for gluster ), throws lots of error messages related to RPC_Transport.

The image creation was successful, but the error messages fills up the console.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHEL 6.6 as Hypervisor using,
libvirt-0.10.2-46.el6.x86_64
qemu-kvm-0.12.1.2-2.445.el6.x86_64
qemu-img-0.12.1.2-2.445.el6.x86_64

with RHGS 3.1 Nightly build installed on RHEL 6.6 -
glusterfs-3.7.0-2.el6rhs

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a VM Image file using 'qemu-img' command
(i.e) qemu-img create -f raw <vm-image-file> 20G

Actual results:
---------------
Observed lots of error messages though the image creation was successful

Expected results:
-----------------
There shouldn't be any error messages seen while creating the image file

Additional info:
----------------
Error message as seen on the console while image creation:
[root@rhs-client10 test]# qemu-img create -f raw gluster://10.70.37.113/rvol/newvm1.img 21G
Formatting 'gluster://10.70.37.113/rvol/newvm1.img', fmt=raw size=22548578304 
[2015-05-19 07:37:01.990771] E [MSGID: 108006] [afr-common.c:3919:afr_notify] 0-rvol-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up.
[2015-05-19 07:37:01.992058] E [rpc-transport.c:512:rpc_transport_unref] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7f8cc0c71fb0] (--> /usr/lib64/libgfrpc.so.0(rpc_transport_unref+0xc0)[0x7f8cc1ad1ec0] (--> /usr/lib64/libgfrpc.so.0(rpc_clnt_unref+0x66)[0x7f8cc1ad39a6] (--> /usr/lib64/libglusterfs.so.0(+0x3054c22a11)[0x7f8cc0c6fa11] (--> /usr/lib64/libglusterfs.so.0(+0x3054c229a5)[0x7f8cc0c6f9a5] ))))) 0-rpc_transport: invalid argument: this
[2015-05-19 07:37:01.992285] E [rpc-transport.c:512:rpc_transport_unref] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7f8cc0c71fb0] (--> /usr/lib64/libgfrpc.so.0(rpc_transport_unref+0xc0)[0x7f8cc1ad1ec0] (--> /usr/lib64/libgfrpc.so.0(rpc_clnt_unref+0x66)[0x7f8cc1ad39a6] (--> /usr/lib64/libglusterfs.so.0(+0x3054c22a11)[0x7f8cc0c6fa11] (--> /usr/lib64/libglusterfs.so.0(+0x3054c229a5)[0x7f8cc0c6f9a5] ))))) 0-rpc_transport: invalid argument: this
[2015-05-19 07:37:01.992490] E [rpc-transport.c:512:rpc_transport_unref] (--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7f8cc0c71fb0] (--> /usr/lib64/libgfrpc.so.0(rpc_transport_unref+0xc0)[0x7f8cc1ad1ec0] (--> /usr/lib64/libgfrpc.so.0(rpc_clnt_unref+0x66)[0x7f8cc1ad39a6] (--> /usr/lib64/libglusterfs.so.0(+0x3054c22a11)[0x7f8cc0c6fa11] (--> /usr/lib64/libglusterfs.so.0(+0x3054c229a5)[0x7f8cc0c6f9a5] ))))) 0-rpc_transport: invalid argument: this

--- Additional comment from SATHEESARAN on 2015-05-19 03:33:42 EDT ---

I have discussed this issue with Raghavendra Talur and he conveyed the fact that this error messages has no impact on the functionality.

But still it fills the console with lots of errors messages.

--- Additional comment from Anand Avati on 2015-06-03 01:16:23 EDT ---

REVIEW: http://review.gluster.org/11041 (rpc: call transport_unref only on non-NULL transport) posted (#2) for review on master by Krishnan Parthasarathi (kparthas)

--- Additional comment from Anand Avati on 2015-06-05 05:59:07 EDT ---

COMMIT: http://review.gluster.org/11041 committed in master by Raghavendra G (rgowdapp) 
------
commit 5441db69f8562a0daa9e6d82aa4279ded0d6e649
Author: Krishnan Parthasarathi <kparthas>
Date:   Tue Jun 2 15:01:53 2015 +0530

    rpc: call transport_unref only on non-NULL transport
    
    BUG: 1227583
    Change-Id: Ifac4dd8c633081483e4eba9d7e5a89837b2a453a
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/11041
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: Raghavendra G <rgowdapp>

Comment 1 Anand Avati 2015-06-05 10:22:14 UTC

REVIEW: http://review.gluster.org/11102 (rpc: call transport_unref only on non-NULL transport) posted (#1) for review on release-3.7 by Krishnan Parthasarathi (kparthas)

Comment 2 Anand Avati 2015-06-09 14:06:50 UTC

COMMIT: http://review.gluster.org/11102 committed in release-3.7 by Raghavendra G (rgowdapp) 
------
commit 4b32816d226b04066b36f569ea34bebfff25d16e
Author: Krishnan Parthasarathi <kparthas>
Date:   Tue Jun 2 15:01:53 2015 +0530

    rpc: call transport_unref only on non-NULL transport
    
    BUG: 1228601
    Change-Id: Ifac4dd8c633081483e4eba9d7e5a89837b2a453a
    Signed-off-by: Krishnan Parthasarathi <kparthas>
    Reviewed-on: http://review.gluster.org/11041
    Reviewed-by: Raghavendra G <rgowdapp>
    Reviewed-on: http://review.gluster.org/11102
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Niels de Vos 2015-06-20 09:50:08 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.2, please reopen this bug report.

glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/packaging/2015-June/000006.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user