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-7881 Lustre <p>This issue was created by maloo for nasf &lt;fan.yong@intel.com&gt;</p> <p>Please provide additional information about the failure here.</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/655b0eb6-ea4e-11e5-8606-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/655b0eb6-ea4e-11e5-8606-5254006e85c2</a>.</p> <p>The log shows</p> <blockquote> <p>/usr/lib64/lustre/tests/sanity-hsm.sh: line 2379: search_and_kill_copytool: command not found<br/> CMD: onyx-49vm6 pgrep -x lhsmtool_posix<br/> onyx-49vm6: 14891<br/> sanity-hsm test_26b: @@@@@@ FAIL: Copytool should have stopped </p></blockquote> LU-7881

sanity-hsm test_26b: @@@@@@ FAIL: Copytool should have stopped

Bug Major Resolved Duplicate Bruno Faccini Maloo Tue, 15 Mar 2016 07:14:29 +0000 Tue, 15 Mar 2016 18:51:34 +0000 Tue, 15 Mar 2016 17:53:41 +0000 0 7 <p>Well, looks like the search_and_kill_copytool() function, internal to sanity-hsm.h, has disappeared ( presumably with Gerrit-change #17499 for <a href="https://jira.whamcloud.com/browse/LU-7136" title="sanity-hsm test_12q failed with &#39;Copytool should have stopped&#39; " class="issue-link" data-issue-key="LU-7136"><del>LU-7136</del></a>) in the meantime patch for <a href="https://jira.whamcloud.com/browse/LU-4640" title="Last unlink should trigger HSM remove by default" class="issue-link" data-issue-key="LU-4640"><del>LU-4640</del></a> (also introducing a new sanity-hsm.sh/test_26b sub-tests that used search_and_kill_copytool() !!) has landed ...</p> <p>Faccini Bruno (bruno.faccini@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/18919" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18919</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7881" title=" sanity-hsm test_26b: @@@@@@ FAIL: Copytool should have stopped " class="issue-link" data-issue-key="LU-7881"><del>LU-7881</del></a> tests: use new functions to kill and verify CT death<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 36ee93fd00a81ae2d492fa89b569dc023fcea64d</p> <p>For the record, I've just seen a failure of this type. It is on code <b>WITHOUT</b> Bruno's patch, linked above.</p> <p><a href="https://testing.hpdd.intel.com/test_sets/aff358a0-ea23-11e5-8186-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/aff358a0-ea23-11e5-8186-5254006e85c2</a></p> <p>Bruno</p> <p>Given that this is causing a lot of test failures Oleg is going to revert the original fix. Could you please combine this test fix into the <a href="https://jira.whamcloud.com/browse/LU-4640" title="Last unlink should trigger HSM remove by default" class="issue-link" data-issue-key="LU-4640"><del>LU-4640</del></a> patch and ensure that test parameters are used to run the affected test 10 times so that we can see for sure that the test fix is robust</p> <p>Thanks</p> <p>Peter</p> <p>Yes will do <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/sad.png" height="16" width="16" align="absmiddle" alt="" border="0"/> but this extra work could have been avoided if patch for <a href="https://jira.whamcloud.com/browse/LU-4640" title="Last unlink should trigger HSM remove by default" class="issue-link" data-issue-key="LU-4640"><del>LU-4640</del></a> had been landed quicker, and not leave patch for <a href="https://jira.whamcloud.com/browse/LU-7136" title="sanity-hsm test_12q failed with &#39;Copytool should have stopped&#39; " class="issue-link" data-issue-key="LU-7136"><del>LU-7136</del></a> to land in between and change sanity-hsm framework. We may be able to detect/control this kind of timing-window race by re-running tests after patches have been merged ? </p> Related LU-4640 LU-7136 Development Rank 1|hzy4hz: Rank (Obsolete) 9223372036854775807 Severity