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-8099 Lustre <p>This issue was created by maloo for sarah_lw &lt;wei3.liu@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/7f355c9e-08a6-11e6-9b34-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/7f355c9e-08a6-11e6-9b34-5254006e85c2</a>.</p> <p>The sub-test test_26 failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>test failed to respond and timed out </pre> </div></div> <p>This is new test added from <a href="https://jira.whamcloud.com/browse/LU-5092" title="nodemap: transfer idmaps between MGS, MDT, OST" class="issue-link" data-issue-key="LU-5092"><del>LU-5092</del></a>, patch landed on Feb 19. After searching Maloo, I found test_26 failed all the time in full test group. it was skipped in review testing as "SLOW"</p> <p>test log</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>CMD: trevis-10vm12 /usr/sbin/lctl nodemap_del c2714 CMD: trevis-10vm12 /usr/sbin/lctl nodemap_del c2715 CMD: trevis-10vm12 /usr/sbin/lctl nodemap_del c2716 </pre> </div></div> <p>Please provide additional information about the failure here.</p> <p>Info required for matching: sanity-sec 26</p> client and server: lustre-master/#3350 RHEL7.2 LU-8099

sanity-sec test_26: test failed to respond and timed out

Bug Minor Open Unresolved Kit Westneat Maloo Wed, 4 May 2016 17:55:56 +0000 Wed, 22 Jun 2022 19:26:11 +0000 Lustre 2.9.0 0 6 <p>Hit the same issue for interop for following config:<br/> Server: 2.8.0 build# 12, EL6.7<br/> Client: master build# 3348 , EL7.2 <br/> <a href="https://testing.hpdd.intel.com/test_sets/5694a11c-08c1-11e6-b5f1-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/5694a11c-08c1-11e6-b5f1-5254006e85c2</a></p> <p>It looks like this test is modified by patch <a href="http://review.whamcloud.com/#/c/16941/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/16941/</a> and passes testing; two cases passing in DNE setup at <a href="https://testing.hpdd.intel.com/test_sets/191fc420-fb87-11e5-acc0-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/191fc420-fb87-11e5-acc0-5254006e85c2</a> and <a href="https://testing.hpdd.intel.com/test_sets/db3442d2-0598-11e6-b5f1-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/db3442d2-0598-11e6-b5f1-5254006e85c2</a>. </p> <p>So, this problem may be cleaned up when patch 16941 lands.</p> <p>That is correct. I can break the test_26 fix into a separate patch if it makes your lives easier. Or perhaps it can be added to the SKIP list until patch 16941 lands? What is the best way to proceed?</p> <p>From the test results the patch <a href="http://review.whamcloud.com/#/c/16941" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/16941</a> looks like sanity-sec is running in about two minutes; <a href="https://testing.hpdd.intel.com/test_sets/e98c1392-275c-11e6-a8f9-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/e98c1392-275c-11e6-a8f9-5254006e85c2</a>. We should submit a patch to remove this test from the SLOW list. </p> Development Rank 1|hzyabr: Rank (Obsolete) 9223372036854775807 Severity