Bug 1194150

Summary: [New] - Brick status is shown as down in RHSC when user creates a rdma volume from Gluster CLI
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: high    
Version: rhgs-3.0CC: annair, asriram, asrivast, divya, dpati, nlevinki, rhs-bugs, rnachimu, sabose
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhsc-3.1.0-57 Doc Type: Bug Fix
Doc Text:
Previously, only TCP ports were monitored. For RDMA only volumes, TCP port is not applicable and these bricks were marked offline. With this fix, both RDMA and TCP ports are monitored and the bricks reflect the correct status.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-29 05:27:21 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: 1191838, 1202842    

Description RamaKasturi 2015-02-19 07:28:23 UTC
Description of problem:
When rdma volume is created from gluster cli and started, brick status in the UI will be shown as down

Version-Release number of selected component (if applicable):
rhsc-3.0.4-1.22.el6rhs.noarch


How reproducible:
Always

Steps to Reproduce:
1. create a rdma volume from CLI by running the command "gluster vol <vol_name> transport rdma <brick1> <brick2>
2. Now start the volume from CLI.
3.

Actual results:
When the volume is synced to UI, brick status will be shown as down as TCP port in the volume status output displays as "N/A."

Expected results:
Brick status should be shown correctly in the UI.

Additional info:

Comment 1 Pavithra 2015-03-17 16:21:55 UTC
Hi Ramesh,

I see this bug being added to the 3.0.4 Known Issues tracker bug. Could you please change the doc type to known issues and fill out the doc text field?

Comment 2 RamaKasturi 2015-03-18 07:48:20 UTC
I do not think it should be added to known issues list, we have to remove it from the 3.0.4 tracker.

It is already mentioned in the console admin guide that RDMA volumes cannot be managed through console.

Comment 3 Pavithra 2015-03-18 11:00:48 UTC
Ramesh, 
Can you please review the edited doc text and sign off?

Comment 4 Ramesh N 2015-03-18 11:22:44 UTC
Doc text is technically correct.

Comment 5 RamaKasturi 2015-06-05 07:29:18 UTC
Verified and works fine with build rhsc-3.1.0-0.58.master.el6.noarch. When an RDMA volume is created from CLI, it gets synced properly in the UI and all the bricks in the UI are shown as UP.

Comment 6 Divya 2015-07-26 07:19:30 UTC
Sahina,

Could you review and sign-off the edited doc text.

Comment 7 Sahina Bose 2015-07-27 04:57:01 UTC
Acked

Comment 9 errata-xmlrpc 2015-07-29 05:27:21 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/RHEA-2015-1494.html