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:
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?
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.
Ramesh, Can you please review the edited doc text and sign off?
Doc text is technically correct.
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.
Sahina, Could you review and sign-off the edited doc text.
Acked
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