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:
guest fail to start with permission denied error when with gluster volume
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64
libvirt-0.10.2-29.el6_5.2.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare gluster server and volume gluster-vol1
[gluster server]# gluster volume info
Volume Name: gluster-vol1
Type: Distribute
Volume ID: 32fe2d1d-7a2a-45d9-8a96-faab68253edd
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 10.66.106.20:/mnt/gluster-volume1
Brick2: 10.66.106.22:/mnt/gluster-volume1
Options Reconfigured:
server.allow-insecure: on
2.create an image by qemu-img on gluster client
[gluster client~]#qemu-img create -f qcow2 gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img 10G
[gluster client~]#qemu-img info gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img
image: gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 136K
cluster_size: 65536
3.define an guest with the disk created in step 2
[gluster client~]#virsh dumpxml rhel6.4-qcow2|grep disk -A 6
<disk type='network' device='disk'>
<driver name='qemu' type='qcow2'/>
<source protocol='gluster' name='gluster-vol1/rhel6.4-qcow2.img'>
<host name='gluster server' port='24007'/>
</source>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
4.start the guest
[gluster client~]#virsh start rhel6.4-qcow2
error: Failed to start domain rhel6.4-qcow2
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/3
qemu-kvm: -drive file=gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img: Permission denied
Actual results:
Expected results:
should succeed starting guest in step 4.
Additional info:
even though i set storage.owner-uid/gid on gluster server, it doesn't work.
error log:
2014-01-13 06:14:06.953+0000: 2622: error : qemuProcessWaitForMonitor:1801 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/3
qemu-kvm: -drive file=gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img: Permission denied
there are two workaround to make it work
1)login to glusterfs server and change owner and group of disk(created from gluster client,here is rhel6.4-qcow2.img) to qemu:qemu
2)login to gluster server and change permission of disk to 666(the default is 600)
sorry for forgot third workaround
3)configure user = "root" and group = "root" in /etc/libvirt/qemu.conf on gluster client, restart libvirt. guest will start without any error.
Description of problem: guest fail to start with permission denied error when with gluster volume Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 libvirt-0.10.2-29.el6_5.2.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare gluster server and volume gluster-vol1 [gluster server]# gluster volume info Volume Name: gluster-vol1 Type: Distribute Volume ID: 32fe2d1d-7a2a-45d9-8a96-faab68253edd Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: 10.66.106.20:/mnt/gluster-volume1 Brick2: 10.66.106.22:/mnt/gluster-volume1 Options Reconfigured: server.allow-insecure: on 2.create an image by qemu-img on gluster client [gluster client~]#qemu-img create -f qcow2 gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img 10G [gluster client~]#qemu-img info gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img image: gluster://gluster server/gluster-vol1/rhel6.4-qcow2.img file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 136K cluster_size: 65536 3.define an guest with the disk created in step 2 [gluster client~]#virsh dumpxml rhel6.4-qcow2|grep disk -A 6 <disk type='network' device='disk'> <driver name='qemu' type='qcow2'/> <source protocol='gluster' name='gluster-vol1/rhel6.4-qcow2.img'> <host name='gluster server' port='24007'/> </source> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> 4.start the guest [gluster client~]#virsh start rhel6.4-qcow2 error: Failed to start domain rhel6.4-qcow2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/3 qemu-kvm: -drive file=gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img: Permission denied Actual results: Expected results: should succeed starting guest in step 4. Additional info: even though i set storage.owner-uid/gid on gluster server, it doesn't work. error log: 2014-01-13 06:14:06.953+0000: 2622: error : qemuProcessWaitForMonitor:1801 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 qemu-kvm: -drive file=gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image gluster+tcp://10.66.106.20:24007/gluster-vol1/rhel6.4-qcow2.img: Permission denied