https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6043 Lustre <p>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 &lt; myconfig.yaml it failed with the following message:</p> <p>&gt;lnetctl import &lt; lnet.yaml<br/> yaml:</p> <ul class="alternate" type="square"> <li>builder:<br/> errno: -1<br/> descr: Failed to handle token:10 <span class="error">&#91;state=6, rc=-2&#93;</span></li> </ul> LU-6043

DLC: lnetctl import does not configure any networks

Bug Major Resolved Fixed Amir Shehata James A Simmons lnet Wed, 17 Dec 2014 23:34:30 +0000 Mon, 12 Jan 2015 18:34:41 +0000 Mon, 12 Jan 2015 18:34:41 +0000 Lustre 2.7.0 Lustre 2.7.0 0 5 <p>Sorry no patch. Not familiar enough with yaml to fix.</p> <p>Amir, </p> <p>Would you please comment on this ticket?</p> <p>Thanks,<br/> James</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/13115" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13115</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6043" title="DLC: lnetctl import does not configure any networks" class="issue-link" data-issue-key="LU-6043"><del>LU-6043</del></a> lnet: Fix YAML FSM and other cleanup<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 90204d6df3a9a0385a7401e56d2ca1a0819c0633</p> <p>Please note that when you do lnetctl export, you'll get output similar to:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">net: - net: lo nid: 0@lo status: up tunables: peer_timeout: 0 peer_credits: 0 peer_buffer_credits: 0 credits: 0 - net: tcp nid: 192.168.205.156@tcp status: up interfaces: 0: eth4 tunables: peer_timeout: 180 peer_credits: 8 peer_buffer_credits: 0 credits: 256 - net: tcp1 nid: 192.168.206.167@tcp1 status: up interfaces: 0: eth5 tunables: peer_timeout: 180 peer_credits: 8 peer_buffer_credits: 0 credits: 256 route: - net: tcp3 gateway: 10.1.1.1@tcp hop: 1 priority: 0 state: up - net: tcp4 gateway: 10.1.1.1@tcp hop: 1 priority: 0 state: up </pre> </div></div> <p>It will dump all currently configured items. To properly test, you'll first need to configure lnet without loading any module parameters. To do that you can issue the following commands:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">modprobe lnet lnetctl lnet configure </pre> </div></div> <p>Then after you configure lnet:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lnetctl <span class="code-keyword">import</span> &lt; config.yaml </pre> </div></div> <p>When you issue the following command it will attempt to configure each item. If the item is already configured it will fail configuring that particular item (example, if you try to reconfig an already existing network it will fail), but it will not stop and will continue to configure the rest of the items.</p> <p>Unfortunately, there is a minor inconsistency in the behavior when you add an existing net vs when you add an existing route. The former will error and the latter will be ignored. We can address this inconsistency in a separate patch (but it's a minor issue)</p> <p>You'll see that when you try to configure the LO Net, since it's part of the configuration but is always configured implicitly and DLC doesn't provide a way to configure the LO Net, it will fail.</p> <p>the output would likely look similar to</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">add: - net: <span class="code-comment">// &lt;-- <span class="code-keyword">this</span> is the error you get when you <span class="code-keyword">try</span> to configure LO </span> errno: -2 descr: <span class="code-quote">"mandatory parameter <span class="code-quote">'<span class="code-keyword">if</span>'</span> not specified. Optionally specify ip2net parameter"</span> - net: errno: 0 descr: <span class="code-quote">"success"</span> - net: errno: 0 descr: <span class="code-quote">"success"</span> - route: errno: 0 descr: <span class="code-quote">"Success"</span> - route: errno: 0 descr: <span class="code-quote">"Success"</span> </pre> </div></div> <p>Currently there is no way to configure LNet from YAML (IE: lnetctl lnet configure). It is assumed that you have already configured LNet either through:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lctl network up or lnetctl lnet configure [--all] </pre> </div></div> <p>If you think it's useful to configure LNet vial YAML, we can address that in a separate patch.</p> <p>So I did a few different approach with your included patch.</p> <p>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 <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>The test of running modprobe lnet; lnetctl net configure; lnetctl import &lt; lnet.yaml still fails with the reported error.</p> <p>sorry was on vacation. </p> <p>Can you please share your lnet.yaml file so I can test on my side.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/13115/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13115/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6043" title="DLC: lnetctl import does not configure any networks" class="issue-link" data-issue-key="LU-6043"><del>LU-6043</del></a> lnet: Fix YAML FSM and other cleanup<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 943469dc33ab665d3908847a21dfee6a3b574505</p> <p>Here is the lnet yaml file giving me headaches.</p> <p>I fixed your issue in a different patch:<br/> <a href="http://review.whamcloud.com/#/c/13304/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/13304/</a></p> <p>You fixed it. Now it works. Thank you.</p> Related LU-6099 LU-6045 Development Project Rank 1|hzx2r3: Rank (Obsolete) 16844 Severity