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-3793 Lustre <p>This issue was created by maloo for Nathaniel Clark &lt;nathaniel.l.clark@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/effa4886-0980-11e3-901c-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/effa4886-0980-11e3-901c-52540035b04c</a>.</p> <p>The sub-test test_66 failed with the following error:</p> <blockquote> <p>MDT start failed</p></blockquote> <p>Info required for matching: conf-sanity 66</p> <p>If test_61 fails (a la <a href="https://jira.whamcloud.com/browse/LU-3792" title="Failure conf-sanity, test_61, error: getxattr failed: -61" class="issue-link" data-issue-key="LU-3792"><del>LU-3792</del></a>) then the state is left partially up, and the setup call in 66 will fail.</p> LU-3793

conf-sanity, subtest test_66 fails due to previous state

Bug Major Resolved Low Priority WC Triage Maloo Tue, 20 Aug 2013 17:56:01 +0000 Fri, 22 Sep 2023 22:23:11 +0000 Thu, 9 Jan 2020 07:09:56 +0000 Lustre 2.5.0 1 3 <p>The goal of this ticket should be to make conf-sanity more robust about resetting the state in the face of failures. Unfortunately, this should take a lower priority than actually fixing the real test failures, since we can never land a patch that has any failures, and ideally we would never see failures and this issue would be moot.</p> <p>Close old bug</p> Related LU-11990 LU-3938 LU-5137 LU-3056 LU-3794 Development Rank 1|hzvyof: Rank (Obsolete) 9810 Severity