Description of problem: ----------------------- Using glusterfs 3.7 nightly build, replica 3 volume was created. While hosting VM images on this volume and spawning VMs from RHEL 7.1, QEMU process logs continuous error message. Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs 3.7 nightly build (glusterfs-3.7dev-0.929.git057d2be.el6.x86_64) RHEL 7.1 - qemu-kvm-1.5.3-86.el7_1.1.x86_64 RHEL 7.1 - libvirt-1.2.8-16.el7_1.2.x86_64 How reproducible: ------------------ Always Steps to Reproduce: ------------------- 1. Create replica 3 volume 2. Optimize volume for virt-store (i.e) gluster volume set <vol-name> group virt 3. Set ownership perms on the volume (i.e) gluster volume set <vol-name> storage.owner-uid 107 gluster volume set <vol-name> storage.owner-uid 107 4. Set an option rpc-auth-allow-insecure in glusterd vol file and restart glusterd 5. Set an option allow-insecure on the volume (i.e) gluster volume set <vol-name> allow-insecure on 6. Restart the volume ( gluster volume stop <vol>, gluster volume start <vol> ) 7. use RHEL 7.1 as a client and create a image file on the volume (i.e) qemu-img create gluster://<server>/<vol>/<image> <size> 8. change the ownership of this file (i.e) chown qemu:qemu <image-file> 9. create a libvirt xml with VM, with disk pointing to disk image on gluster volume <disk type='network' device='disk'> <driver name='qemu' type='raw'/> <source protocol='gluster' name='repv/vm1.img'> <host name='10.70.37.113'/> </source> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> 10. create a vm (i.e) virsh define <xml-file-definition> 11. Start the vm (i.e) virsh start <vm-name> 12. Look for any error messages under /var/log/libvirt/qemu/ (i.e) less /var/log/libvirt/qemu/<vm-name>.log Actual results: --------------- There are continuous log messages logged Sample - [2015-04-08 17:45:53.524939] E [rpc-clnt.c:362:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7f610ba83516] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f6111d3625e] (--> /lib64/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f6111d3636e] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x9c)[0x7f6111d37cfc] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x48)[0x7f6111d384b8] ))))) 0-repv-client-2: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2015-04-08 17:45:53.523944 (xid=0x172) Expected results: ----------------- There should be any error messages logged in the qemu log file for the VM
I haven't set the option rpc-auth-allow-insecure to 'on', on all glusterd vol files. In this test, I have made this changes only on one glusterd. After making changes on all glusterd, I no longer see this problem, Closing this bug. Will re-open this bug, if the problem is encountered again