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.
Description of problem:
-----------------------
qemu provides native driver for glusterfs ( which uses libgfapi of glusterfs ), for the VMs to access their disk images.
If the host section contains more than one host, I am unable to start the VM
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHEL 7.3
RHGS 3.2.0 ( interim build, not yet GA'ed )
qemu-img-1.5.3-126.el7.x86_64
ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch
qemu-kvm-common-1.5.3-126.el7.x86_64
libvirt-daemon-driver-qemu-2.0.0-10.el7.x86_64
qemu-kvm-1.5.3-126.el7.x86_64
libvirt-daemon-config-network-2.0.0-10.el7.x86_64
libvirt-python-2.0.0-2.el7.x86_64
libvirt-daemon-driver-storage-2.0.0-10.el7.x86_64
libvirt-daemon-2.0.0-10.el7.x86_64
libvirt-daemon-driver-qemu-2.0.0-10.el7.x86_64
libvirt-daemon-driver-interface-2.0.0-10.el7.x86_64
libvirt-daemon-driver-network-2.0.0-10.el7.x86_64
libvirt-daemon-config-nwfilter-2.0.0-10.el7.x86_64
libvirt-daemon-driver-nodedev-2.0.0-10.el7.x86_64
libvirt-2.0.0-10.el7.x86_64
libvirt-daemon-driver-nwfilter-2.0.0-10.el7.x86_64
libvirt-daemon-driver-secret-2.0.0-10.el7.x86_64
libvirt-client-2.0.0-10.el7.x86_64
libvirt-daemon-driver-lxc-2.0.0-10.el7.x86_64
How reproducible:
-----------------
Always
Steps to Reproduce:
-------------------
1. Create a VM image on the replica 3 gluster volume ( there are 3 gluster servers )
2. Create a VM ( by editing the vm.xml to make following changes )
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='gluster' name='rep3vol/vm7.img'>
<host name='dhcp37-54.lab.eng.blr.redhat.com' port='24007'/>
<host name='dhcp37-138.lab.eng.blr.redhat.com' port='24007'/>
<host name='dhcp37-50.lab.eng.blr.redhat.com' port='24007'/>
</source>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
3. Start the VM
Actual results:
---------------
Unable to start the VM
Expected results:
-----------------
VM should get started
Additional info:
----------------
Errors as seen :
[root@rhs-client10 repvol]# virsh start vm7
error: Failed to start domain vm7
error: internal error: process exited while connecting to monitor: 2016-11-14T08:29:44.266843Z qemu-kvm: -drive file.driver=gluster,file.volume=rep3vol,file.path=/vm7.img,file.server.0.type=tcp,file.server.0.host=dhcp37-54.lab.eng.blr.redhat.com,file.server.0.port=24007,file.server.1.type=tcp,file.server.1.host=dhcp37-138.lab.eng.blr.redhat.com,file.server.1.port=24007,file.server.2.type=tcp,file.server.2.host=dhcp37-50.lab.eng.blr.redhat.com,file.server.2.port=24007,format=raw,if=none,id=drive-virtio-disk0,werror=stop,rerror=stop: could not open disk image drive-virtio-disk0: The 'gluster' block driver requires a file name
Description of problem: ----------------------- qemu provides native driver for glusterfs ( which uses libgfapi of glusterfs ), for the VMs to access their disk images. If the host section contains more than one host, I am unable to start the VM Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHEL 7.3 RHGS 3.2.0 ( interim build, not yet GA'ed ) qemu-img-1.5.3-126.el7.x86_64 ipxe-roms-qemu-20160127-5.git6366fa7a.el7.noarch qemu-kvm-common-1.5.3-126.el7.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7.x86_64 qemu-kvm-1.5.3-126.el7.x86_64 libvirt-daemon-config-network-2.0.0-10.el7.x86_64 libvirt-python-2.0.0-2.el7.x86_64 libvirt-daemon-driver-storage-2.0.0-10.el7.x86_64 libvirt-daemon-2.0.0-10.el7.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7.x86_64 libvirt-daemon-driver-interface-2.0.0-10.el7.x86_64 libvirt-daemon-driver-network-2.0.0-10.el7.x86_64 libvirt-daemon-config-nwfilter-2.0.0-10.el7.x86_64 libvirt-daemon-driver-nodedev-2.0.0-10.el7.x86_64 libvirt-2.0.0-10.el7.x86_64 libvirt-daemon-driver-nwfilter-2.0.0-10.el7.x86_64 libvirt-daemon-driver-secret-2.0.0-10.el7.x86_64 libvirt-client-2.0.0-10.el7.x86_64 libvirt-daemon-driver-lxc-2.0.0-10.el7.x86_64 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Create a VM image on the replica 3 gluster volume ( there are 3 gluster servers ) 2. Create a VM ( by editing the vm.xml to make following changes ) <disk type='network' device='disk'> <driver name='qemu' type='raw'/> <source protocol='gluster' name='rep3vol/vm7.img'> <host name='dhcp37-54.lab.eng.blr.redhat.com' port='24007'/> <host name='dhcp37-138.lab.eng.blr.redhat.com' port='24007'/> <host name='dhcp37-50.lab.eng.blr.redhat.com' port='24007'/> </source> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> 3. Start the VM Actual results: --------------- Unable to start the VM Expected results: ----------------- VM should get started Additional info: ---------------- Errors as seen : [root@rhs-client10 repvol]# virsh start vm7 error: Failed to start domain vm7 error: internal error: process exited while connecting to monitor: 2016-11-14T08:29:44.266843Z qemu-kvm: -drive file.driver=gluster,file.volume=rep3vol,file.path=/vm7.img,file.server.0.type=tcp,file.server.0.host=dhcp37-54.lab.eng.blr.redhat.com,file.server.0.port=24007,file.server.1.type=tcp,file.server.1.host=dhcp37-138.lab.eng.blr.redhat.com,file.server.1.port=24007,file.server.2.type=tcp,file.server.2.host=dhcp37-50.lab.eng.blr.redhat.com,file.server.2.port=24007,format=raw,if=none,id=drive-virtio-disk0,werror=stop,rerror=stop: could not open disk image drive-virtio-disk0: The 'gluster' block driver requires a file name