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-15151 Lustre <p>This issue was created by maloo for Elena &lt;elena.gryaznova@hpe.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/4f01fe03-3433-4b2b-9ca9-ebce8607c27b" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/4f01fe03-3433-4b2b-9ca9-ebce8607c27b</a></p> <p>test_119 PASSED, but</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>mds1: ssh: Could not resolve hostname mds1: Name or service not known </pre> </div></div> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> conf-sanity test_119 - </p> LU-15151

conf-sanity test_119: mds1: ssh: Could not resolve hostname mds1: Name or service not known

Bug Minor Resolved Fixed Elena Gryaznova Maloo Fri, 22 Oct 2021 18:35:00 +0000 Fri, 5 Nov 2021 07:35:55 +0000 Wed, 3 Nov 2021 03:42:49 +0000 Lustre 2.15.0 0 4 <p>It looks like this was introduced by patch <a href="https://review.whamcloud.com/27753" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/27753</a> "<tt><a href="https://jira.whamcloud.com/browse/LU-9699" title="osp_obd_connect()) ASSERTION( osp-&gt;opd_connects == 1 ) failed" class="issue-link" data-issue-key="LU-9699"><del>LU-9699</del></a> osp: don't assert on OSP duplicating</tt>".</p> <p>The <tt>wait_update_cond()</tt> call in test_119 should take a hostname as an argument instead of a facet name.</p> <p>"Elena Gryaznova &lt;elena.gryaznova@hpe.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/45369" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45369</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15151" title="conf-sanity test_119: mds1: ssh: Could not resolve hostname mds1: Name or service not known" class="issue-link" data-issue-key="LU-15151"><del>LU-15151</del></a> tests: use facet check intead of node check<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 59432387b259d06b0bee1b2e769ee2b639b9c46d</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/45369/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45369/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15151" title="conf-sanity test_119: mds1: ssh: Could not resolve hostname mds1: Name or service not known" class="issue-link" data-issue-key="LU-15151"><del>LU-15151</del></a> tests: use facet check instead of node check<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: dc27b1c3ea1852617012753a3cce1f6c76b164af</p> <p>Landed for 2.15</p> <p>conf-sanity/119 times out every time with the patch:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> COMMIT TESTED PASSED FAILED COMMIT DESCRIPTION dc27b1c3ea 3 0 3 BAD LU-15151 tests: use facet check instead of node check fa36c6b0b9 3 3 0 GOOD LU-15160 kernel: kernel update SLES12 SP5 [4.12.14-122.91.2] </pre> </div></div> <p>Alex, what do you have in your config for <tt>$mds1_HOST</tt> (maps to <tt>$mds_HOST</tt> if unset)? Can the client $PDSH to that node (should be a no-op if it is a single client).</p> <p>According to the Gerrit Janitor test logs, the test is taking 1200s to finish, and the <tt>wait_update_facet_cond()</tt> is continually timing out, but this does not cause an error return:</p> <p><a href="https://testing-archive.whamcloud.com/gerrit-janitor/19360/results.html" class="external-link" target="_blank" rel="nofollow noopener">https://testing-archive.whamcloud.com/gerrit-janitor/19360/results.html</a></p> <p>I'm not sure if that is how this test is supposed to work or not, but 1200s is a long time and probably the test should be added to the <tt>SLOW</tt> list.</p> <p>I use default local.sh as a configuration, this is a single VM. and yes, wait_update_facet_cond() just times out while I set an explicit limit for a whole test (conf-sanity) in this case. I don't quite understand the test - it doesn't fail if wait_update_facet_cond() times out. what's the point of this waiting?</p> Related LU-9699 Development Rank 1|i0285r: Rank (Obsolete) 9223372036854775807 Severity