[LU-6340] DLC: /etc/rc.d/init.d/lnet doesn't configure lnet exactly as defined in lnet.conf

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.7.0
• Environment: lustre-b2_7 build #29
• Severity: 3
• Assignee: Amir Shehata (Inactive)
• Reporter: Sarah Liu

Description

After running /etc/rc.d/init.d/lnet start, it doesn't configure lnet exactly as defined in /etc/sysconf/lnet.conf. Router is missing, net are not the exact same.

This is a minor issue, Amir has suggested 1 line change can fix this problem .

the lnet.conf looks like

[root@eagle-54vm3 modprobe.d]# more /etc/sysconfig/lnet.conf 
net:
    - net: lo
      nid: 0@lo
      status: up
      tunables:
          peer_timeout: 0
          peer_credits: 0
          peer_buffer_credits: 0
          credits: 0
    - net: tcp1
      nid: 192.168.201.180@tcp1
      status: up
      interfaces:
          0: eth1
      tunables:
          peer_timeout: 181
          peer_credits: 8
          peer_buffer_credits: 0
          credits: 256
route:
    - net: tcp
      gateway: 192.168.201.101@tcp1
      hop: 1
      priority: 0
      state: up
[root@eagle-54vm3 modprobe.d]# 

after running lnet start check the system

[root@eagle-54vm3 modprobe.d]# lnetctl net show -v
net:
    - net: lo
      nid: 0@lo
      status: up
      tunables:
          peer_timeout: 0
          peer_credits: 0
          peer_buffer_credits: 0
          credits: 0
    - net: tcp
      nid: 10.100.4.198@tcp
      status: up
      tunables:
          peer_timeout: 180
          peer_credits: 8
          peer_buffer_credits: 0
          credits: 256
    - net: tcp1
      nid: 192.168.201.180@tcp1
      status: up
      interfaces:
          0: eth1
      tunables:
          peer_timeout: 181
          peer_credits: 8
          peer_buffer_credits: 0
          credits: 256
[root@eagle-54vm3 modprobe.d]# lnetctl route show -v
[root@eagle-54vm3 modprobe.d]#

Issue Links

• is duplicated by: LU-7474 Using lnet init script and lnetctl brings up tcp interface

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/14000/
Subject: LU-6340 lnet: LNet startup script fix
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: f7259a01bb3f18f571d6ed8ecf7c95e1f9521bbb

[Gerrit Updater]

Amir Shehata ([e-mail]) uploaded a new patch: http://review.whamcloud.com/14000
Subject: LU-6340 lnet: LNet startup script fix
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: e3b4da8c93b7421802e3b8d03c6ef2b913eb56c5

[Amir Shehata (Inactive)]

The issue here is that "lctl network up" is used to bring up LNet, but that configures everything in module parameters. The fix is to use lnetctl to configure LNet only if the proper lnet YAML configuration file is present. This way the script remains backward compatible.

[Andreas Dilger]

Amir, can you please provide a patch, in case we have another 2.7 RC5.