Description of problem:
I've tried both systemd & libvirt mailing list but nothing, nobody commented.
I have a simple domains:
<disk type='network' device='disk'>
<driver name='qemu' type='raw'/>
<source protocol='gluster' name='QEMU-VMs/rhel-work3.qcow2'>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
and they work fine but fail to autostart.
Errors I see:
failed to initialize gluster connection (src=0x7f9424266350 priv=0x7f94242922b0): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work2': failed to initialize gluster connection (src=0x7f9
failed to initialize gluster connection (src=0x7f942423fef0 priv=0x7f9424256320): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work3': failed to initialize gluster connection (src=0x7f9
failed to initialize gluster connection (src=0x7f9424261b20 priv=0x7f94242a18b0): Transport endpoint is
internal error: Failed to autostart VM 'rhel-work1': failed to initialize gluster connection (src=0x7f9
I tried to make systemd libvirtd to wait for gluster:
but if that's all required then, well, still fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(In reply to lejeczek from comment #0)
> Description of problem:
> I've tried both systemd & libvirt mailing list but nothing, nobody commented.
Peter responded a few minutes before you created this bz. Does it help?
I'm not sure if you're seeing the same issue I saw.
Basically glusterd would not start properly, and
when it did, I often got errors about the transport.
My temporary fix is to disable glusterd and
libvirtd, then put the following into /etc/rc.local:
until [ -d /vms/.trashcan ] || [ $counter -eq 10 ]; do
service glusterd restart
counter=`expr $counter + 1`
[ -d /vms/.trashcan ] && systemctl start libvirtd
(This is a fully patched CentOS 7.3 server if that
makes any difference.)
Actually, I think that - After=glusterd.service - works for me. There were lots of updates since I filed the report, still on gluster 3.8, 3.8.9-1.el7.x86_64 but it works now. I edited with --full, like:
I did not manage to reproduce the issue with a host running glusterfs-3.8.4-1.el7. I suspect that the systemd service for glusterd is marked as started prior to glusterd actually working properly.
If the bug reproduces again please reopen this BZ and attach also logs for glusterd, since libvirtd can't do much if the storage does not work.