+++ This bug was initially created as a clone of Bug #1689097 +++ +++ This bug was initially created as a clone of Bug #1586201 +++ TL;DR: We need the ability to control the gluster logging from libvirt/QEMU when using the gluster driver. +++ This bug was initially created as a clone of Bug #1447694 +++ QEMU is unable to store Gluster specific debugging logs under /var/run/gluster/... This is because QEMU runs as user "qemu" and does not have write permissions there. This debugging (called 'statedump') can be triggered from the Gluster CLI which sends an event to QEMU (when libgfapi is used). When the glusterfs packages make sure that a group "gluster" has write permissions to /var/run/gluster/, could the qemu(-kvm-rhev) package be adjusted to have the "qemu" user in the "gluster" group? This would allow more debugging options that help with potential issues when QEMU runs with disk-images over libgfapi.so. --- Additional comment from Worker Ant on 2019-03-15 07:41:40 UTC --- REVIEW: https://review.gluster.org/22364 (gfapi: provide an api for setting statedump path) posted (#1) for review on master by Amar Tumballi --- Additional comment from Amar Tumballi on 2019-06-14 05:28:24 UTC --- The patch is now merged. --- Additional comment from Worker Ant on 2019-07-25 08:23:12 UTC --- REVIEW: https://review.gluster.org/23103 (gfapi: provide version for statedump path) posted (#1) for review on release-7 by Amar Tumballi
https://review.gluster.org/#/c/glusterfs/+/23096/ fixes the issue.