Description of problem: ----------------------- QEMU uses native glusterfs driver ( which uses libgfapi ) to provides VM ability to access to the disks that resides on gluster volume When generating statedump of gfapi application (QEMU), QEMU doesn't have permission to write to statedump path ( /var/run/gluster ) and doesn't generates statedump. Only the applications that runs with 'root' privilege could write to the directory - /var/run/gluster There should be a proper way for applications that doesn't have root privilege to write to /var/run/gluster Version-Release number of selected component (if applicable): ------------------------------------------------------------- mainline 3.10 3.8 How reproducible: ------------------ Always Steps to Reproduce: -------------------- 1. Create a VM that runs with disk accessed using QEMU's native driver for glusterfs (gfapi) 2. Trigger statedump from gluster node # gluster volume statedump <vol> client <hypervisor-IP/FQDN>:<QEMU-PID> Actual results: --------------- No statedump dumped by QEMU process under /var/run/gluster QEMU user doesn't have privilege to write to /var/run/gluster Expected results: ----------------- statedump available under /var/run/gluster
Thanks Neils for figuring out the actual problem that QEMU doesn't have permission to write to /var/run/gluster directory. Possible solutions as suggested by Neils 1. One approach would be to create a "gluster" group and give the group permissions to write to /var/run/gluster/... 2. Other 'fixes' include setting ACLs on the directory so that specified users can write there.because many daemons have a "home directory" that does not exist, it probably is not a good idea to use $HOME to store statedumps.
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
Requested ideas on the oVirt devel list too: http://lists.ovirt.org/pipermail/devel/2017-April/030262.html
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#4) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#5) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/17122 (packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps) posted (#6) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/17122 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 0e50c4b3ea734456c14e2d7a578463999bd332c3 Author: Kaleb S. KEITHLEY <kkeithle> Date: Wed Apr 26 08:11:56 2017 -0400 packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps gfapi has the ability to take statedumps. However, if the application using gfapi isn't running with root privs the statedump file can't be written to the default location, i.e. /var/run/gluster. Change-Id: I97d8919ef8b8cd4775e1a206f939a2bf0046786d BUG: 1445569 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: https://review.gluster.org/17122 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report. glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/