[LU-6043] DLC: lnetctl import does not configure any networks

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.7.0
• Affects Version/s: Lustre 2.7.0
• Labels: lnet
• Severity: 3
• Project: Dynamic LNET Configuration
• Assignee: Amir Shehata (Inactive)
• Reporter: James A Simmons

Description

I can bring up a network with lctl net up and once up I used lnetctl export to create a configuration file. After I brought down the network and attempted to bring the network usig lnetctl import < myconfig.yaml it failed with the following message:

>lnetctl import < lnet.yaml
yaml:

• builder:
  errno: -1
  descr: Failed to handle token:10 [state=6, rc=-2]

Issue Links

• is related to: LU-6045 DLC: Address a minor inconsistency between net and route adding behavior
• is related to: LU-6099 DLC: YAML output must adhere to parsing rules

Comments

[James A Simmons]

You fixed it. Now it works. Thank you.

[Amir Shehata (Inactive)]

I fixed your issue in a different patch:
http://review.whamcloud.com/#/c/13304/

[James A Simmons]

Here is the lnet yaml file giving me headaches.

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/13115/
Subject: LU-6043 lnet: Fix YAML FSM and other cleanup
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 943469dc33ab665d3908847a21dfee6a3b574505

[Amir Shehata (Inactive)]

sorry was on vacation.

Can you please share your lnet.yaml file so I can test on my side.

[James A Simmons]

So I did a few different approach with your included patch.

First I found without the patch lnetctl net configure --all only adds lo interface after I run modprobe lnet. The system is configured for o2ib as well. With the patch it does work

The test of running modprobe lnet; lnetctl net configure; lnetctl import < lnet.yaml still fails with the reported error.