Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Desription:
gluster exported qcow2 img cannot be used by latest qemu-kvm-rhev/libvirt
PLEASE NOTE, THIS ISSUE NOT REPRODUCED WITH glusterfs-server-3.8.4-1.el7rhgs.x86_64
SO IT'A REGRESSION
How reproducible:
100%
Versions:
kernel-3.10.0-514.2.1.el7.x86_64
libvirt-2.0.0-10.el7_3.1.x86_64
qemu-img-rhev-2.6.0-27.el7.x86_64
qemu-kvm-common-rhev-2.6.0-27.el7.x86_64
qemu-kvm-rhev-2.6.0-27.el7.x86_64
glusterfs-libs-3.8.4-3.el7rhgs.x86_64
glusterfs-cli-3.8.4-3.el7rhgs.x86_64
glusterfs-3.8.4-3.el7rhgs.x86_64
glusterfs-api-3.8.4-3.el7rhgs.x86_64
glusterfs-fuse-3.8.4-3.el7rhgs.x86_64
glusterfs-client-xlators-3.8.4-3.el7rhgs.x86_64
glusterfs-server-3.8.4-3.el7rhgs.x86_64
Reproduce steps:
1. Prepare a gluster server in localhost, as follow
Add "option rpc-auth-allow-insecure on" in /etc/glusterfs/glusterd.vol
#vim /etc/glusterfs/glusterd.vol
volume management
...
option rpc-auth-allow-insecure on
...
# service glusterd restart
Stopping glusterd: [ OK ]
Starting glusterd: [ OK ]
# mkdir /br1
# chmod -R 777 /br1
# setenforce 0
# iptables -F
# gluster volume create gluster-vol1 localhost:/br1 force
# gluster volume set gluster-vol1 server.allow-insecure on
# gluster volume start gluster-vol1
# gluster volume set gluster-vol1 nfs.disable on
# qemu-img create -f qcow2 /br1/test.qcow2 1G
# service glusterd restart
2. edit a vm and insert following virtual dis
#virsh edit avocado-vt-vm1
<disk type='network' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source protocol='gluster' name='gluster-vol1/test.qcow2'>
<host name='127.0.0.1' port='24007'/>
</source>
<target dev='vdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</disk>
3. start the guest failed, as follow:
# virsh start avocado-vt-vm1
error: Failed to start domain avocado-vt-vm1
error: internal error: qemu unexpectedly closed the monitor: [2016-11-08 06:42:30.011107] I [MSGID: 104045] [glfs-master.c:91:notify] 0-gfapi: New graph 7367692d-7576-3230-2d30-312e72687473 (0) coming up
[2016-11-08 06:42:30.011160] I [MSGID: 114020] [client.c:2356:notify] 0-gluster-vol1-client-0: parent translators are ready, attempting connect on transport
[2016-11-08 06:42:30.014892] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gluster-vol1-client-0: changing port to 49152 (from 0)
[2016-11-08 06:42:30.018213] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gluster-vol1-client-0: Using Program GlusterFS 3.3, Num (1298437), Version (330)
[2016-11-08 06:42:30.019558] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gluster-vol1-client-0: Connected to gluster-vol1-client-0, attached to remote volume '/br1'.
[2016-11-08 06:42:30.019576] I [MSGID: 114047] [client-handshake.c:1233:client_setvolume_cbk] 0-gluster-vol1-client-0: Server and Client lk-version numbers are not same, reopening th
Actual result:
Cannot start vm due to gluster error
Expected result:
Vm should be started correctly
Additional info:
1. if we create a raw img in gluster vol, and use that raw img in vm's virtual disk, everything is OK
2. This is not reproduced with glusterfs*-3.8.4-1, with below rpms
# rpm -qa | egrep "libvirt-2|qemu-kvm|kernel-3|glusterfs"
glusterfs-libs-3.8.4-1.el7rhgs.x86_64
glusterfs-rdma-3.8.4-1.el7rhgs.x86_64
qemu-kvm-common-rhev-2.6.0-27.el7.x86_64
glusterfs-3.8.4-1.el7rhgs.x86_64
glusterfs-api-3.8.4-1.el7rhgs.x86_64
glusterfs-fuse-3.8.4-1.el7rhgs.x86_64
glusterfs-server-3.8.4-1.el7rhgs.x86_64
glusterfs-api-devel-3.8.4-1.el7rhgs.x86_64
glusterfs-geo-replication-3.8.4-1.el7rhgs.x86_64
glusterfs-debuginfo-3.8.4-1.el7rhgs.x86_64
libvirt-2.0.0-10.el7_3.1.x86_64
kernel-3.10.0-514.2.1.el7.x86_64
glusterfs-client-xlators-3.8.4-1.el7rhgs.x86_64
glusterfs-cli-3.8.4-1.el7rhgs.x86_64
glusterfs-devel-3.8.4-1.el7rhgs.x86_64
glusterfs-events-3.8.4-1.el7rhgs.x86_64
qemu-kvm-rhev-2.6.0-28.el7.x86_64
Desription: gluster exported qcow2 img cannot be used by latest qemu-kvm-rhev/libvirt PLEASE NOTE, THIS ISSUE NOT REPRODUCED WITH glusterfs-server-3.8.4-1.el7rhgs.x86_64 SO IT'A REGRESSION How reproducible: 100% Versions: kernel-3.10.0-514.2.1.el7.x86_64 libvirt-2.0.0-10.el7_3.1.x86_64 qemu-img-rhev-2.6.0-27.el7.x86_64 qemu-kvm-common-rhev-2.6.0-27.el7.x86_64 qemu-kvm-rhev-2.6.0-27.el7.x86_64 glusterfs-libs-3.8.4-3.el7rhgs.x86_64 glusterfs-cli-3.8.4-3.el7rhgs.x86_64 glusterfs-3.8.4-3.el7rhgs.x86_64 glusterfs-api-3.8.4-3.el7rhgs.x86_64 glusterfs-fuse-3.8.4-3.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-3.el7rhgs.x86_64 glusterfs-server-3.8.4-3.el7rhgs.x86_64 Reproduce steps: 1. Prepare a gluster server in localhost, as follow Add "option rpc-auth-allow-insecure on" in /etc/glusterfs/glusterd.vol #vim /etc/glusterfs/glusterd.vol volume management ... option rpc-auth-allow-insecure on ... # service glusterd restart Stopping glusterd: [ OK ] Starting glusterd: [ OK ] # mkdir /br1 # chmod -R 777 /br1 # setenforce 0 # iptables -F # gluster volume create gluster-vol1 localhost:/br1 force # gluster volume set gluster-vol1 server.allow-insecure on # gluster volume start gluster-vol1 # gluster volume set gluster-vol1 nfs.disable on # qemu-img create -f qcow2 /br1/test.qcow2 1G # service glusterd restart 2. edit a vm and insert following virtual dis #virsh edit avocado-vt-vm1 <disk type='network' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source protocol='gluster' name='gluster-vol1/test.qcow2'> <host name='127.0.0.1' port='24007'/> </source> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> 3. start the guest failed, as follow: # virsh start avocado-vt-vm1 error: Failed to start domain avocado-vt-vm1 error: internal error: qemu unexpectedly closed the monitor: [2016-11-08 06:42:30.011107] I [MSGID: 104045] [glfs-master.c:91:notify] 0-gfapi: New graph 7367692d-7576-3230-2d30-312e72687473 (0) coming up [2016-11-08 06:42:30.011160] I [MSGID: 114020] [client.c:2356:notify] 0-gluster-vol1-client-0: parent translators are ready, attempting connect on transport [2016-11-08 06:42:30.014892] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gluster-vol1-client-0: changing port to 49152 (from 0) [2016-11-08 06:42:30.018213] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gluster-vol1-client-0: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2016-11-08 06:42:30.019558] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gluster-vol1-client-0: Connected to gluster-vol1-client-0, attached to remote volume '/br1'. [2016-11-08 06:42:30.019576] I [MSGID: 114047] [client-handshake.c:1233:client_setvolume_cbk] 0-gluster-vol1-client-0: Server and Client lk-version numbers are not same, reopening th Actual result: Cannot start vm due to gluster error Expected result: Vm should be started correctly Additional info: 1. if we create a raw img in gluster vol, and use that raw img in vm's virtual disk, everything is OK 2. This is not reproduced with glusterfs*-3.8.4-1, with below rpms # rpm -qa | egrep "libvirt-2|qemu-kvm|kernel-3|glusterfs" glusterfs-libs-3.8.4-1.el7rhgs.x86_64 glusterfs-rdma-3.8.4-1.el7rhgs.x86_64 qemu-kvm-common-rhev-2.6.0-27.el7.x86_64 glusterfs-3.8.4-1.el7rhgs.x86_64 glusterfs-api-3.8.4-1.el7rhgs.x86_64 glusterfs-fuse-3.8.4-1.el7rhgs.x86_64 glusterfs-server-3.8.4-1.el7rhgs.x86_64 glusterfs-api-devel-3.8.4-1.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-1.el7rhgs.x86_64 glusterfs-debuginfo-3.8.4-1.el7rhgs.x86_64 libvirt-2.0.0-10.el7_3.1.x86_64 kernel-3.10.0-514.2.1.el7.x86_64 glusterfs-client-xlators-3.8.4-1.el7rhgs.x86_64 glusterfs-cli-3.8.4-1.el7rhgs.x86_64 glusterfs-devel-3.8.4-1.el7rhgs.x86_64 glusterfs-events-3.8.4-1.el7rhgs.x86_64 qemu-kvm-rhev-2.6.0-28.el7.x86_64