Bug 1302202

Summary:	Unable to get the client statedump, as /var/run/gluster directory is not available by default
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	build	Assignee:	Milind Changire <mchangir>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.7	CC:	amukherj, bugs, ndevos, nlevinki, rhs-bugs, sankarshan, sasundar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1302200	Environment:
Last Closed:	2016-04-19 07:21:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1298118, 1302200
Bug Blocks:

Description Milind Changire 2016-01-27 07:00:33 UTC

+++ This bug was initially created as a clone of Bug #1302200 +++

+++ This bug was initially created as a clone of Bug #1298118 +++

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

--- Additional comment from Milind Changire on 2016-01-14 00:21:45 EST ---

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?

--- Additional comment from Niels de Vos on 2016-01-25 10:03:02 EST ---

(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.

Comment 1 Vijay Bellur 2016-02-29 05:59:08 UTC

REVIEW: http://review.gluster.org/13541 (build: make /var/run/gluster available everywhere) posted (#1) for review on release-3.7 by Milind Changire (mchangir)

Comment 2 Vijay Bellur 2016-02-29 08:10:30 UTC

REVIEW: http://review.gluster.org/13541 (build: make /var/run/gluster available everywhere) posted (#2) for review on release-3.7 by Niels de Vos (ndevos)

Comment 3 Vijay Bellur 2016-03-06 02:51:47 UTC

COMMIT: http://review.gluster.org/13541 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 60504a1a926fabdcddbded90ff28f56f50ada6b7
Author: Milind Changire <mchangir>
Date:   Wed Jan 27 12:59:58 2016 +0530

    build: make /var/run/gluster available everywhere
    
    /var/run/gluster was only avialable with glusterfs-server package.
    Move it to primary glusterfs package so that client installations as
    well as server installations can generate state-dump in that directory.
    
    Cherry picked from commit 759b63536c676f4b4fa135ea62d74dff021778e4:
    > Change-Id: I1cdd2c5118ac657b2dab4f9669c6657484b8c600
    > BUG: 1302200
    > Signed-off-by: Milind Changire <mchangir>
    > Reviewed-on: http://review.gluster.org/13296
    > Reviewed-by: Kaleb KEITHLEY <kkeithle>
    > Tested-by: Kaleb KEITHLEY <kkeithle>
    > CentOS-regression: Gluster Build System <jenkins.com>
    > Reviewed-by: Niels de Vos <ndevos>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Smoke: Gluster Build System <jenkins.com>
    
    Change-Id: I1cdd2c5118ac657b2dab4f9669c6657484b8c600
    BUG: 1302202
    Signed-off-by: Milind Changire <mchangir>
    Reviewed-on: http://review.gluster.org/13541
    Reviewed-by: Niels de Vos <ndevos>
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Mike McCune 2016-03-28 23:03:07 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Kaushal 2016-04-19 07:21:58 UTC

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.7.9, please open a new bug report.

glusterfs-3.7.9 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] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user