Bug 1665677 - volume create and transport change with rdma failed
Summary: volume create and transport change with rdma failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: rdma
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Atin Mukherjee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-12 13:42 UTC by Chris
Modified: 2019-07-15 06:54 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-07-15 06:54:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Chris 2019-01-12 13:42:28 UTC 
Description of problem:

Cannot create volume with transport tcp,rdma
If i use tcp or rdma only creation works

Version-Release number of selected component (if applicable):
4.1.6-1 and 5.2-1

How reproducible:
Everytime

Steps to Reproduce:
1. gluster volume create vg0 replica 3 transport tcp,rdma <brick1> <brick2> <brick3>

Actual results:
volume create: vg0: failed: Failed to create volume files

Expected results:
volume create: vg0: success: please start the volume to access data

Additional info:
After successful creation of Volume with rdma or tcp a change to tcp,rdma also fails.
Comment 2 Amar Tumballi 2019-07-15 06:54:52 UTC 
I see https://review.gluster.org/#/c/glusterfs/+/22851/ is merged, which should fix the issue.

But, please note, from glusterfs-8.0, the RDMA transport would be not supported. And with that info, inclined to close the issue as WONTFIX.
Note You need to log in before you can comment on or make changes to this bug.