libdapl2: PCI RoCe IB dapltest does not recognize updated names of /etc/dat.conf entries

[bugproxy]

== Comment: #0 - Helmut Grauer - 2016-03-04 04:59:10 ==
Hi
Configure IB for dapltest
Ethernet Interface
np0s0 Link encap:Ethernet HWaddr 82:01:14:32:f0:90
          inet addr:10.100.80.2 Bcast:10.100.255.255 Mask:255.255.0.0
          inet6 addr: fe80::8001:14ff:fe32:f090/64 Scope:Link
          inet6 addr: fd00:10:100::ff:80:2/80 Scope:Global
          inet6 addr: fd00:10:100:0:8001:14ff:fe32:f090/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:25938 errors:0 dropped:0 overruns:0 frame:0
          TX packets:253 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8228251 (8.2 MB) TX bytes:21494 (21.4 KB)

Installing related packages for dapltest

librdmacm-dev install
librdmacm1 install
librdmacm1-dbg install
dapl2-utils install
libibumad3 install
libibverbs-dev install
libibverbs1 install
libmlx4-1 install
libmlx4-1-dbg install
libmlx4-dev install
libmlx5-1 install
libmlx5-1-dbg install
libmlx5-dev install

configure /etc/dat.conf
ofa-v2-cma-roe-eth2 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "eth2 0" ""
test u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "enP1p0s0 0" ""
s83lp02_dapl u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "enp0s0 0" ""
ofa-v2-cma-roe-eth3 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "eth3 0" ""
ofa-v2-scm-roe-mlx4_0-1 u2.0 nonthreadsafe default libdaploscm.so.2 dapl.2.0 "mlx4_0 1" ""
ofa-v2-scm-roe-mlx4_0-2 u2.0 nonthreadsafe default libdaploscm.so.2 dapl.2.0 "mlx4_0 2" ""

dapltest is only working if I specify
 ofa-v2-scm-roe-mlx4_0-1

dapltest -T S -D ofa-v2-scm-roe-mlx4_0-1
Dapltest: Service Point Ready - ofa-v2-scm-roe-mlx4_0-1

If I used the self defined name in dat.conf
it will not recognize

root@s83lp02:~# dapltest -T S -D s83lp02_dapl
DT_cs_Server: Could not open s83lp02_dapl (DAT_INTERNAL_ERROR )
DT_cs_Server (s83lp02_dapl): Exiting.

I will add to Bugzilla SOSReport and dbg.info

Helmut

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1553183/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Christian Ehrhardt  (paelzer)]

FYI - blocked on RoCE setup in RT 89459

[Frank Heimes (fheimes)]

On 17.04 / Zesty several RoCE (rdma, ib, etc.) related packages were updated to the latest upstream releases.
Based on these 'version bumped' packages the dapltest tool now recognizes changes in /etc/dat.conf.

In addition to the default entries I added for example the following two test entries:
$ grep test /etc/dat.conf
test1 u2.0 nonthreadsafe default libdaploscm.so.2 dapl.2.0 "mlx4_0 1" ""
test2 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "enP1p0s0 0" ""
$

The dapltest tool recognizes these now without crashing:
$ dapltest -T S -D test1
Dapltest: Service Point Ready - test1
^C
$ dapltest -T S -D test2
Dapltest: Service Point Ready - test2
^C
$

Would be good if this can be verified by the bug reporter as well (on Zesty),
incl. any potential follow-on steps for the dapltest in detail,
to make sure that entire undertaking works.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-08 10:57 EDT-------
Hi
have done retest with 16.04.01
Still the same problem as mentioned in Bugzilla, if I try to use self defined name in dat.conf server connection is will close.

oot@s35lp07:~# uname -a
Linux s35lp07 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux
fa-v2-mthca0-2u u2.0 nonthreadsafe default libdaploucm.so.2 dapl.2.0 "mthca0 2" ""
ofa-v2-cma-roe-eth2 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "eth2 0" ""
ofa-v2-cma-roe-eth3 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "eth3 0" ""
ofa-v2-scm-roe-mlx4_0-1 u2.0 nonthreadsafe default libdaploscm.so.2 dapl.2.0 "mlx4_0 1" ""
ofa-v2-scm-roe-mlx4_0-2 u2.0 nonthreadsafe default libdaploscm.so.2 dapl.2.0 "mlx4_0 2" ""
enP1s32 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "enP1s32 0" ""
VLAN203 u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0 "VLAN203 0" ""

oot@s35lp07:~# dapltest -T S -D ofa-v2-scm-roe-mlx4_0-1
Dapltest: Service Point Ready - ofa-v2-scm-roe-mlx4_0-1

oot@s35lp07:~# dapltest -T S -D enP1s32
DT_cs_Server: Could not open enP1s32 (DAT_INTERNAL_ERROR )
DT_cs_Server (enP1s32): Exiting.

Will add SOS report again.

Helmut

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2017-09-08 10:59 EDT-------

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2017-09-08 11:00 EDT-------

[Frank Heimes (fheimes)]

Hi Helmut, looks like you re-tested on 16.04.
Not sure if you can see Launchpad comment #5 in IBM's Bugzilla system:
https://bugs.launchpad.net/ubuntu/+source/dapl/+bug/1553183/comments/5
It describes that the fixes landed in Zesty / 17.04 only, due to the massive updates/modifications that were required.

(And btw. 16.04.1 is obsolete anyway, doing a normal update will bring you to 16.04.3 these days ...)

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-11 03:05 EDT-------
Hi Frank,
thanks for the information
Helmut

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-03-09 04:36 EDT-------
@Canonial: Fix committed since 2017-12-13, any updates here ?

[Frank Heimes (fheimes)]

According to comment #5 and #10 the packages are already released for Zesty and higher.
It's just not marked as Fix Released because we wanted to wait for final confirmation from your side (#5). If not needed it can be change to Fix Released now ...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-05-22 04:16 EDT-------
IBM bugzilla status-> closed; Fix Released by Canonical, for further found bugs, a new LP will be created