Bug 1398581

Summary:	gluster-template: '/var/lib/misc/glusterfsd/' fs is not persisted after RHGS container restart
Product:	Red Hat Gluster Storage	Reporter:	Mohamed Ashiq <mliyazud>
Component:	heketi	Assignee:	Mohamed Ashiq <mliyazud>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	cns-3.4	CC:	hchiramm, madam, mliyazud, pprakash, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	CNS 3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 21:57:51 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:
Bug Depends On:
Bug Blocks:	1385247

Description Mohamed Ashiq 2016-11-25 10:50:40 UTC

Description of problem:
/var/lib/misc/glusterfsd is used for debugging in geo-replication. This should be persistent in the container.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

/var/lib/misc/glusterfsd is not persistent on re spawns of the RHGS container.

Additional info:

/var/lib/misc/glusterfsd is not persistent on re spawns of the RHGS container.

Comment 5 Mohamed Ashiq 2016-11-25 11:42:31 UTC

Patch is upstream under review

https://github.com/heketi/heketi/pull/586

Comment 6 Mohamed Ashiq 2016-11-30 05:15:26 UTC

(In reply to Mohamed Ashiq from comment #5)
> Patch is upstream under review
> 
> https://github.com/heketi/heketi/pull/586

The Patch is merged upstream.

Comment 7 Michael Adam 2016-12-12 14:22:36 UTC

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=528156

Comment 10 Prasanth 2016-12-27 10:03:11 UTC

Verified as fixed in the latest heketi build

Comment 11 errata-xmlrpc 2017-01-18 21:57:51 UTC

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/RHEA-2017-0148.html