Bug 1494339

Summary:	Heketi pod stops working when being restarted or deleted
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	rhgs-volmanager-container	Assignee:	Raghavendra Talur <rtalur>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	cns-3.6	CC:	aos-bugs, aos-storage-staff, hchiramm, hongkliu, knarra, madam, mliyazud, pprakash, rcyriac, rhs-bugs, sankarshan, storage-qa-internal, suprasad
Target Milestone:	---
Target Release:	CNS 3.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1490980	Environment:
Last Closed:	2017-10-11 06:57:33 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:
Bug Blocks:	1445448

Comment 2 Raghavendra Talur 2017-09-22 05:30:07 UTC

The error is that heketi fails to open the db file with read write access or with read write lock. This fails all operations that requires read write access.

Comment 4 errata-xmlrpc 2017-10-11 06:57:33 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://access.redhat.com/errata/RHEA-2017:2876

Comment 5 RamaKasturi 2018-11-15 14:27:42 UTC

setting the qe_test_coverage flag to '-' because i see that the heketi pod is being deleted using --now and with the latest releases with out using this flag heketi pod can be restarted.