Bug 1656910

Summary: Heketi service hung not able to create volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: mmariyan
Component: heketiAssignee: John Mulligan <jmulligan>
Status: CLOSED DUPLICATE QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, aos-storage-staff, bkunal, hchiramm, jarrpa, jmulligan, kramdoss, madam, pprakash, rhs-bugs, rtalur, sankarshan, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: ---   
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: 2019-08-13 18:41:20 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:

Description mmariyan 2018-12-06 16:12:46 UTC 
Description of problem:

PVC provisioning didn't work with CNS despite all pods were up and running and no errors in logs.PVC which used the glusterfs storage class were not bound. Recreation of the heketi pod solved this issue.

=>This time not able to find any logs about heketi is stopped/hunged

=>


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

How reproducible:


Actual results:

Not able to find any logs about heketi service stopped/hung. not able to provion new pvc.

Expected results:

It  should show some logs about heketi service. or should implement some checks to see when the heketi pod is in a hung state and self heal the system when possible.



StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:
Comment 2 Yaniv Kaul 2019-04-01 06:56:30 UTC 
Status?
Comment 4 Bipin Kunal 2019-05-08 10:12:15 UTC 
@John,
  Any further update on this?

@Mariyan: I see no follow up from you on this bug, aren't you answerable to the customer?
Comment 8 John Mulligan 2019-08-13 18:41:20 UTC 

*** This bug has been marked as a duplicate of bug 1636912 ***