-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: add a test to enable and test rdma connect #1759
Conversation
dsharma-dc
commented
Oct 23, 2024
- Added a simple test to create and publish a nexus. Connect it over rdma.
- The connect API is modified to take transport parameter.
- The test automatically detects a suitable interface to create a soft-RDMA device, creates it and deletes it at the end of the test.
fde28b2
to
e6fd96c
Compare
The changes for composer dependencies are here: openebs/mayastor-dependencies#96 |
e6fd96c
to
5c64d04
Compare
f542244
to
f4d3f01
Compare
bors try |
tryBuild failed: |
f4d3f01
to
acc6c2d
Compare
bors try |
tryBuild failed: |
CI machines have been setup with required modules now. bors try |
tryMerge conflict. |
acc6c2d
to
15026cc
Compare
15026cc
to
fd8ae17
Compare
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
I tried running the test manually and I notice the issue is that rxe rdma device is not getting correct IP address of the chosen interface assigned. This is the issue that we see when overlay network is present. As a result rdma listen is failing. I'll mark the test as IP assigned to rdma device on eth0 (compare only last byte of dot decimal notation) Actual IP of eth0 from ifconfig
|
Signed-off-by: Diwakar Sharma <[email protected]>
fd8ae17
to
f54f358
Compare
bors try |
tryBuild succeeded: |
bors merge |
Build succeeded: |