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-16185 Lustre <p>This issue was created by maloo for Andreas Dilger &lt;adilger@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run:<br/> <a href="https://testing.whamcloud.com/test_sets/cbe19d9e-7c85-41e5-96cb-e56f1601e43c" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/cbe19d9e-7c85-41e5-96cb-e56f1601e43c</a></p> <p>test_212 failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>discover: - primary nid: 10.240.27.140@tcp Multi-Rail: True peer ni: - nid: 10.240.27.140@tcp Fail local discover ping to set LNET_PEER_REDISCOVER flag error: net_drop_add: option 'local_error' unrecognized /usr/sbin/lnetctl discover --force 10.240.26.0@tcp discover: - primary nid: 10.240.26.0@tcp Multi-Rail: True peer ni: - nid: 10.240.26.0@tcp sanity-lnet test_212: @@@@@@ FAIL: Discovery should have failed </pre> </div></div> <p>It looks like this is failing 100% on 2.12.x branches for aarch64 or ppcle64, but not x86 clients. </p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity-lnet test_212 - Discovery should have failed</p> LU-16185

sanity-lnet test_212: Discovery should have failed

Bug Minor Resolved Fixed Frank Sehr Maloo arm Fri, 23 Sep 2022 21:32:29 +0000 Fri, 4 Nov 2022 18:05:29 +0000 Thu, 3 Nov 2022 21:55:12 +0000 Lustre 2.12.9 0 3 <p>Frank investigated this and it looks like this is a duplicate of <a href="https://jira.whamcloud.com/browse/LU-13701" title="sanity-lnet test_205: @@@@@@ FAIL: Should have failed" class="issue-link" data-issue-key="LU-13701"><del>LU-13701</del></a> and needs patch <a href="https://review.whamcloud.com/40036" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40036</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-13701" title="sanity-lnet test_205: @@@@@@ FAIL: Should have failed" class="issue-link" data-issue-key="LU-13701"><del>LU-13701</del></a> utils: fix usage of getopt_long in portals</tt>" cherry-picked back to b2_12. </p> <p>fixed with patch <a href="https://review.whamcloud.com/40036" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40036</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-13701" title="sanity-lnet test_205: @@@@@@ FAIL: Should have failed" class="issue-link" data-issue-key="LU-13701"><del>LU-13701</del></a> utils: fix usage of getopt_long in portals</tt>"</p> <p>As far as I can see it would affect the LNet add drop/delay rules on aarch64. Maybe I should add it? </p> <p>Backporting it to b2_12 is fine if you have the time, though I don't think it is a high priority. </p> Duplicate LU-13701 Development Rank 1|i0314n: Rank (Obsolete) 9223372036854775807 Severity