[LU-11858] LNet interfaces can be undefined when defining nets with --ip2net

Mon, 14 Jan 2019 21:09:25 +0000

This issue can prevent the output of 'lnetctl export --backup' from being used with 'lnetctl import'.

Note the two different formats for the ip2net string. Both are, historically, valid, but the second form results in a bug where the interfaces for that net are undefined:

sles15s01:~ # lustre_rmmod
sles15s01:~ # modprobe lnet
sles15s01:~ # lnetctl lnet configure
sles15s01:~ # lnetctl net add --ip2net "tcp1(eth0) 192.168.2.[21-50]"
sles15s01:~ # lnetctl net add --ip2net "tcp2 192.168.2.[21-50]"
sles15s01:~ # lnetctl export --backup
net:
    - net type: tcp1
      local NI(s):
        - interfaces:
              0: eth0
          tunables:
              peer_timeout: 180
              peer_credits: 8
              peer_buffer_credits: 0
              credits: 256
          CPT: "[0,1,2,3]"
    - net type: tcp2
      local NI(s):
        - tunables:
              peer_timeout: 180
              peer_credits: 8
              peer_buffer_credits: 0
              credits: 256
          CPT: "[0,1,2,3]"
global:
    numa_range: 0
    max_intf: 200
    discovery: 1
sles15s01:~ # lnetctl export --backup > /tmp/lnet.yml
sles15s01:~ # lnetctl lnet unconfigure
sles15s01:~ # lustre_rmmod
sles15s01:~ # modprobe lnet
sles15s01:~ # lnetctl lnet configure
sles15s01:~ # lnetctl import < /tmp/lnet.yml
add:
    - net:
          errno: 0
          descr: "success"
    - net:
          errno: -2
          descr: "missing mandatory parameters in NI config: 'interface'"
    - max_interfaces:
          errno: 0
          descr: "success"
    - numa_range:
          errno: 0
          descr: "success"
    - discovery:
          errno: 0
          descr: "success"
sles15s01:~ #

Whamcloud Community JIRA

[LU-11858] LNet interfaces can be undefined when defining nets with --ip2net