Description of problem: ----------------------- /var/run/gluster should automatically created after installing glusterfs fuse client rpms Consequences of this issue is that the user unable to get the to get the statedump of fuse mount process ( client side statedump ) Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1.1 ( glusterfs-3.7.1-16.el7 ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Look for the director /var/run/gluster (ie) ls /var/run/gluster Actual results: --------------- /var/run/gluster directory is not available after install client rpms Expected results: ----------------- /var/run/gluster should be created by the client rpms Additional info: ---------------- Consequence of this issue would be user unable to get the client statedump Workaround is to create : /var/run/gluster and then initiate statedump
As per downstream glusterfs.spec.in, /var/run/gluster is packaged only with the glusterfs-server RPM and specifically excluded for non-server RPM packaging. So any client only RPM install will not have that directory created. Also, as per Niels comment for his upstream patch on making /var/run/gluster available, it should have been made available for native client installs as well ... but its not so in downstream packaging. I'll have to move the directory packaging in downstream RPMs to a common RPM like the primary package 'glusterfs'. Is this acceptable?
(In reply to Milind Changire from comment #1) ... > I'll have to move the directory packaging in downstream RPMs to a common RPM > like the primary package 'glusterfs'. > > Is this acceptable? Yes, that should be acceptable. Please make sure to file a bug+patch for this in upstream as well if the problem exists there still.
Tested with glusterfs-3.8.4-3.el7 and glusterfs-3.8.4-3.el6 /var/run/gluster directory is created by glusterfs package # rpm -qf /var/run/gluster/ glusterfs-3.8.4-3.el7.x86_64 # rpm -qf /var/run/gluster glusterfs-3.8.4-3.el6.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html