Bug 1194138

Summary: When RDMA init fails, the resources are not cleaned up properly
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rdmaAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.0CC: aavati, amainkar, annair, nlevinki, rcyriac, rkavunga, rtalur, rwheeler, vagarwal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.0.4   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0.46-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-26 06:36:08 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: 1181044, 1182947    

Description SATHEESARAN 2015-02-19 05:44:31 UTC 
Description of problem:
-----------------------
When RDMA init fails, the resources are not cleaned up properly.
Consequence is that glusterd crashes, when taking glusterd statedump.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.6.0.45-1.el6rhs

How reproducible:
-----------------
Consistent

Steps to Reproduce:
-------------------
1. Start glusterd on non-RDMA setup

Actual results:
---------------
RDMA init fails to free the resources

Expected results:
------------------
When RDMA init failed, all the associated resources should be cleaned up properly
Comment 1 SATHEESARAN 2015-02-19 05:46:02 UTC 
This issue blocks getting glusterd statedump and hence blocks verification of that bug 1181044
Comment 2 Mohammed Rafi KC 2015-02-19 10:19:06 UTC 
https://code.engineering.redhat.com/gerrit/#/c/42282/
Comment 3 Mohammed Rafi KC 2015-02-19 10:30:44 UTC 
Root cause identified as: When an rdma init is failed, the created private variable is not freeing the resources, that's making the the address out of bound.
Comment 4 SATHEESARAN 2015-03-03 18:33:02 UTC 
Earlier without the fix, getting the glusterd statedump would crash, as the variable reached out-of-bounds

With this fix, glusterd statedump doesn't crash and hence verifies that there is no out-of-bounds error hit, when RDMA is not initialized.

Tested with glusterfs-3.6.0.46-1.el6rhs
Comment 6 errata-xmlrpc 2015-03-26 06:36:08 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/RHBA-2015-0682.html