Bug 1570976

Summary: [GSS] OCP pods fail to mount gluster block volumes after cluster being rebooted
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Oonkwee Lim <olim>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: Nitin Goyal <nigoyal>
Severity: high Docs Contact:
Priority: urgent    
Version: cns-3.6CC: amukherj, ansverma, aos-bugs, bkozdemb, dsundqvi, ekuric, hbustam, jarrpa, jcall, jokerman, kborup, kramdoss, madam, mjudeiki, mmccomas, olim, pkarampu, prasanna.kalever, rhs-bugs, sankarshan, shberry, tkarlsso, vinug, weshi
Target Milestone: ---   
Target Release: CNS 3.10   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-19.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1540080 Environment:
Last Closed: 2018-09-12 09:25:34 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: 1537170, 1540080, 1598322    
Bug Blocks: 1568861, 1573420    

Comment 7 Jose A. Rivera 2018-04-30 12:17:21 UTC
Hmm... if you used cns-deploy and experience this problem you should open a different PR against the gluster-block component of the Red Hat Gluster Storage product. I won't be very good at helping solve that one.

Comment 12 Jose A. Rivera 2018-04-30 13:09:53 UTC
If you could clarify at this point: Is this a reproducible issue in cns-deploy that you are experiencing, or is this an issue in a specific installation that needs to be fixed?

Comment 20 Nitin Goyal 2018-08-28 14:04:44 UTC
as per comment 19 i verified bug https://bugzilla.redhat.com/show_bug.cgi?id=1598322 which is working properly, So marking this as verified.

Comment 22 errata-xmlrpc 2018-09-12 09:25:34 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-2018:2691