Bug 1188685 - Current Volume status command doesn't show RDMA port for tcp,rdma type volume
Summary: Current Volume status command doesn't show RDMA port for tcp,rdma type volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rdma
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.0.4
Assignee: Mohammed Rafi KC
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1182947
TreeView+ depends on / blocked
 
Reported: 2015-02-03 14:23 UTC by Vivek Agarwal
Modified: 2016-02-18 00:03 UTC (History)
11 users (show)

Fixed In Version: glusterfs-3.6.0.46-1
Doc Type: Bug Fix
Doc Text:
Previously, for "tcp,rdma" type volumes, the RDMA port details was hidden from all types of volume details, such as volume status, volume details, xml output etc. Due to this, the user could not see the port details of RDMA bricks. To fix this issue, the following changes were made: *A new column for volume status is introduced that will print rdma port for a brick. If the rdma brick is not available the value will be zero. Changed the port colum to tcp port. *In volume details, an extra entry for rdma port is added and the existing port is changed to tcp port. *For xml output, a new tag called "ports", and two sub tags tcp, rdma is created . The old port tag is retained for backward compatibility.
Clone Of:
Environment:
Last Closed: 2015-03-26 06:35:57 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0682 0 normal SHIPPED_LIVE Red Hat Storage 3.0 enhancement and bug fix update #4 2015-03-26 10:32:55 UTC

Description Vivek Agarwal 2015-02-03 14:23:14 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Mohammed Rafi KC 2015-02-04 02:51:07 UTC 
Description of problem:

volume status command doesn't show rdma port for tcp,rdma type volumes. The value under port column is tcp port. 

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

master

How reproducible:

100%

Steps to Reproduce:
1.create a tcp,rdma transport type volume
2.start the volume
3.gluster volume status

Actual results:

showing only tcp port.

Expected results:

It should give information about both tcp port and rdma port
Comment 2 Mohammed Rafi KC 2015-02-13 07:41:05 UTC 
upstream patch:
http://review.gluster.org/#/c/9191/
Comment 3 Raghavendra G 2015-02-18 14:03:44 UTC 
https://code.engineering.redhat.com/gerrit/#/c/42191/
Comment 4 SATHEESARAN 2015-03-09 07:19:01 UTC 
Verified with glusterfs-3.6.0.48-1.el6rhs

Now 'gluster volume status' && 'gluster volume status --detail' showing up RDMA ports. Performed the following tests and based on that marking this bug as VERIFIED.

Tests are,
1. Getting volume status on all nodes for a RDMA volume of any type
2. Getting volume status on the node not having bricks for RDMA volume
3. Getting volume status, when the brick is not running
4. Getting volume status, when all the bricks are up and running
5. Getting volume status, from all the nodes in the cluster

Created the test cases, 
https://tcms.engineering.redhat.com/case/468094/?from_plan=6243
https://tcms.engineering.redhat.com/case/468196/?from_plan=6243
https://tcms.engineering.redhat.com/case/468197/?from_plan=6243
https://tcms.engineering.redhat.com/case/468095/?from_plan=6243
https://tcms.engineering.redhat.com/case/468096/?from_plan=6243
https://tcms.engineering.redhat.com/case/468198/?from_plan=6243
https://tcms.engineering.redhat.com/case/468199/?from_plan=6243
Comment 5 Bhavana 2015-03-17 07:23:35 UTC 
Hi Rafi,

Can you please update the doc text for this bug.
Comment 6 Bhavana 2015-03-24 03:29:22 UTC 
Hi Rafi,



The doc text is updated. review the same and sign off if it looks ok.
Comment 7 Mohammed Rafi KC 2015-03-24 04:57:46 UTC 
doc looks good to me.
Comment 9 errata-xmlrpc 2015-03-26 06:35:57 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
Note You need to log in before you can comment on or make changes to this bug.