Bug 1494339 - Heketi pod stops working when being restarted or deleted
Summary: Heketi pod stops working when being restarted or deleted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhgs-volmanager-container
Version: cns-3.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: CNS 3.6
Assignee: Raghavendra Talur
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1445448
TreeView+ depends on / blocked
 
Reported: 2017-09-22 05:27 UTC by Raghavendra Talur
Modified: 2018-11-15 14:27 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1490980
Environment:
Last Closed: 2017-10-11 06:57:33 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1490980 0 unspecified CLOSED Heketi pod stops working when beging restarted or deleted 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2017:2876 0 normal SHIPPED_LIVE rhgs-volmanager-container bug fix and enhancement update 2017-10-11 11:11:34 UTC

Internal Links: 1490980

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.


Note You need to log in before you can comment on or make changes to this bug.