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-17373 Lustre <p>When running llmount.sh. Update to mgc_requeue_timeout_min could fail. One reason for that could be not setting of passwordless ssh to self. While this is not fatel. Mounts on server/client would still work , as by that time the mounts have already been done. However, the llmount.sh scripts breaks in between soon after this. Wtih the false error message as below. </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>rocky9a: Host key verification failed. pdsh@rocky9a: rocky9a: ssh exited with exit code 255 + return 255</pre> </div></div> LU-17373

Add check under init_param_vars() when update to mgc_requeue_timeout_min fails

Bug Minor Open Unresolved WC Triage Arshad Hussain Mon, 18 Dec 2023 10:40:35 +0000 Fri, 22 Dec 2023 02:01:42 +0000 0 3 <p>"Arshad Hussain &lt;arshad.hussain@aeoncomputing.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53487" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53487</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-17373" title="Add check under init_param_vars() when update to mgc_requeue_timeout_min fails" class="issue-link" data-issue-key="LU-17373">LU-17373</a> tests: Add check after updating mgc_requeue_timeout_min<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: a4415c860bd6399c97911eb30bbe0801769376ed</p> <p>Is this something failing in Autotest or just your local test config? I think fixing this specific subtest is missing the higher-level issue. </p> <p>The test-framework.sh code should not be trying to do "ssh" to the local node, but it seems possible if it is confused that the hostname does not match the "client" node name? Otherwise, there is a specific check in <tt>do_node()</tt> if the target node matches the local hostname and "<tt>no_dsh</tt>" is used to execute the command directly. </p> <p>It seems that <tt>do_node()</tt> needs to get smarter and track all local interfaces to determine whether the client hostname resolves to a local interface and avoids "ssh" entirely, since it is always slower than executing the command directly.</p> <p>That would solve this issue for all tests instead of just this one test. </p> <blockquote><p>Is this something failing in Autotest or just your local test config? ...</p></blockquote> <p>This is local test setup.</p> <p> </p> <blockquote><p>The test-framework.sh code should not be trying to do "ssh" to the local node, but it seems possible if it is confused that the hostname does not match the "client" node name? Otherwise, there is a specific check in do_node() if the target node matches the local hostname and "no_dsh" is used to execute the command directly.</p> <p>It seems that do_node() needs to get smarter and track all local interfaces to determine whether the client hostname resolves to a local interface and avoids "ssh" entirely, since it is always slower than executing the command directly.</p> <p>That would solve this issue for all tests instead of just this one test.</p></blockquote> <p>Thanks for the clarification. I will update the patch with your suggestion.</p> Development Rank 1|i0457r: Rank (Obsolete) 9223372036854775807 Severity