[LU-14539] LNet: lnet shouldn't need to be configured explicitly when lustre is loaded

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Labels: config lnet lnetctl startup
• Severity: 3
• Assignee: WC Triage
• Reporter: Serguei Smirnov

Description

If using 

modprobe lustre 

with lustre.conf containing

options lnet networks="o2ib0(ib0,ib1),tcp0(eno1)"

this results in the following network configuration:

# lnetctl net show
net:
    - net type: lo
      local NI(s):
        - nid: 0@lo
          status: up
    - net type: o2ib
      local NI(s):
        - nid: 10.1.0.20@o2ib
          status: up
          interfaces:
              0: ib0
        - nid: 10.2.0.20@o2ib
          status: up
          interfaces:
              0: ib1
    - net type: tcp
      local NI(s):
        - nid: 10.0.0.68@tcp
          status: up
          interfaces:
              0: eno1

However, attempts to make changes fail until "lnetctl lnet configure" is executed:

# lnetctl net del --net tcp
del:
    - net:
          errno: -22
          descr: "cannot del network: Invalid argument"
# lnetctl lnet configure
# lnetctl net del --net tcp
# lnetctl net show
net:
    - net type: lo
      local NI(s):
        - nid: 0@lo
          status: up
    - net type: o2ib
      local NI(s):
        - nid: 10.1.0.20@o2ib
          status: up
          interfaces:
              0: ib0
        - nid: 10.2.0.20@o2ib
          status: up
          interfaces:
              0: ib1