[LU-5854] DLC: lnetctl import failed as Failed to handle token:2 [state=0, rc=-1] Created: 03/Nov/14  Updated: 02/Dec/14  Resolved: 02/Dec/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: Lustre 2.7.0

Type: Bug Priority: Major
Reporter: Sarah Liu Assignee: Amir Shehata (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-2456 Dynamic LNet Config Main Development ... Resolved
Severity: 3
Rank (Obsolete): 16390

 Description   

the lnetctl import failed to import an yaml file; also the /etc/rc.d/init.d/lnet failed load the configuration yaml file under /etc/sysconfig/network-scripts

[root@onyx-28 ~]# lnetctl import /tmp/lnetconfig.yaml 
yaml:
    - builder:
          errno: -1
          descr: Failed to handle token:2 [state=0, rc=-1]
[root@onyx-28 ~]# more /tmp/lnetconfig.yaml 
net:
    - nid: 0@lo
      status: up
      tunables:
          peer_timeout: 0
          peer_credits: 0
          peer_buffer_credits: 0
          credits: 0
          CPTs:  0
    - nid: 10.2.4.74@tcp
      status: up
      interfaces:
          0: eth0
      tunables:
          peer_timeout: 180
          peer_credits: 8
          peer_buffer_credits: 0
          credits: 256
          CPTs:  0
route:
    - net: o2ib
      gateway: 10.2.4.65@tcp
      hop: 1
      priority: 0
      state: up
routing:
[root@onyx-28 ~]# 


 Comments   
Comment by Amir Shehata (Inactive) [ 04/Nov/14 ]

Currently the appropriate input YAML should look like:

net:
    - net: tcp3
      status: up
      interfaces:
         0: eth4
      tunables:
          peer_timeout: 180
          peer_credits: 8
          peer_buffer_credits: 0
          credits: 256

The problem is that the input and output YAML format is different. We should make them consistent, so that output can be fed as input.

Comment by Amir Shehata (Inactive) [ 04/Nov/14 ]

http://review.whamcloud.com/#/c/12556/

Comment by Jodi Levi (Inactive) [ 02/Dec/14 ]

Patch landed to Master.

Generated at Sat Feb 10 01:55:06 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.