Bug 1001893

Summary: qemu-kvm segmentation fault while boot guest from glusterfs with wrong host name
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijay Bellur <vbellur>
Component: glusterfsAssignee: Vijay Bellur <vbellur>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: acathrow, amarts, asias, bsarathy, chayang, huding, juzhang, mazhang, mkenneth, qzhang, rhs-bugs, shaines, vagarwal, vbellur, virt-maint
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.34rhs-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 996829 Environment:
Last Closed: 2013-11-27 15:34:31 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: 998778    
Bug Blocks: 996829    

Comment 1 Amar Tumballi 2013-08-28 11:00:20 UTC
Vijay, it has rhs-2.1.z flag, do you want it after GA? or should we take it in for 'rhs-2.1.0' itself? I saw the patch https://code.engineering.redhat.com/gerrit/#/c/12073, and it looks good. Also, as the procedure @ the time, need 'blocker' flag to take the patch in, so let me know how do you want to proceed.

Comment 2 SATHEESARAN 2013-10-08 14:06:13 UTC
With the glusterfs-3.4.0.34rhs-1 update, I am not seeing this issue.
Tested with RHEL 6.5 Beta
Marking it as VERIFIED

Version Info
============

[root@rhs-client8 ~]# rpm -qa | grep qemu
qemu-kvm-tools-0.12.1.2-2.406.el6.x86_64
gpxe-roms-qemu-0.9.7-6.10.el6.noarch
qemu-kvm-0.12.1.2-2.406.el6.x86_64
qemu-img-0.12.1.2-2.406.el6.x86_64

[root@rhs-client8 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 6.5 Beta (Santiago)
Kernel \r on an \m

[root@rhs-client8 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.5 Beta (Santiago)
[root@rhs-client8 ~]# rpm -qa | grep glusterfs
glusterfs-libs-3.4.0.34rhs-1.el6.x86_64
glusterfs-fuse-3.4.0.34rhs-1.el6.x86_64
glusterfs-3.4.0.34rhs-1.el6.x86_64
glusterfs-api-devel-3.4.0.34rhs-1.el6.x86_64
glusterfs-rdma-3.4.0.34rhs-1.el6.x86_64
glusterfs-api-3.4.0.34rhs-1.el6.x86_64
glusterfs-devel-3.4.0.34rhs-1.el6.x86_64

Steps
======
[root@rhs-client8 ~]# /usr/libexec/qemu-kvm  -drive file=gluster://glusterfs-server/simple/rhel64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=0 
qemu-kvm: -drive file=gluster://glusterfs-server/simple/rhel64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads: Gluster connection failed for server=glusterfs-server port=0 volume=simple image=rhel64.qcow2 transport=tcp

qemu-kvm: -drive file=gluster://glusterfs-server/simple/rhel64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image gluster://glusterfs-server/simple/rhel64.qcow2: Transport endpoint is not connected
[root@rhs-client8 ~]# glusterfs -V
glusterfs 3.4.0.34rhs built on Oct  8 2013 02:04:48
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2013 Red Hat, Inc. <http://www.redhat.com/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.

Comment 3 SATHEESARAN 2013-10-08 14:27:54 UTC
FIXED IN VERSION should be glusterfs-3.4.0.34rhs-1 
Raising the NEEDINFO for changing fixed in version

Comment 5 errata-xmlrpc 2013-11-27 15:34:31 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.

http://rhn.redhat.com/errata/RHBA-2013-1769.html