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-1189 Lustre <p>This issue was created by maloo for Minh Diep &lt;mdiep@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/8f2e25a2-662c-11e1-92b1-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/8f2e25a2-662c-11e1-92b1-5254004bbbd3</a>.</p> <p><a href="https://maloo.whamcloud.com/test_sets/8f2e25a2-662c-11e1-92b1-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/8f2e25a2-662c-11e1-92b1-5254004bbbd3</a></p> <p>When the last subtest is skipped, the entire test is marked failed even everything else passed</p> LU-1189

restore_lustre_params() needs run on active server nodes

Bug Minor Resolved Fixed Jian Yu Maloo Mon, 5 Mar 2012 11:40:24 +0000 Tue, 5 Sep 2017 13:26:55 +0000 Fri, 26 Apr 2013 15:48:00 +0000 Lustre 2.4.0 Lustre 2.1.4 Lustre 2.4.0 Lustre 2.1.5 0 5 <p>I can't reproduce this issue in the lab. I noticed that the failures are on group 'failover'. I wonder if this is specific issue to failover testing</p> <p>Lustre Tag: v2_1_4_RC1<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-b2_1/159/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_1/159/</a><br/> Distro/Arch: RHEL6.3/x86_64<br/> Test Group: failover</p> <p>The same issue existed: <a href="https://maloo.whamcloud.com/test_sets/064bc9ea-4bb6-11e2-aa80-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/064bc9ea-4bb6-11e2-aa80-52540035b04c</a></p> <p>actually, I found an error after all the subtest completed</p> <p>09:02:17:PASS 11b (376s)<br/> 09:02:17:<br/> 09:02:17: SKIP: replay-vbr test_12a skipping ALWAYS excluded test 12a<br/> 09:02:17:CMD: client-27vm3 lctl set_param -n mdt.lustre-MDT0000.commit_on_sharing 0<br/> 09:02:17:client-27vm3: error: set_param: /proc/</p> {fs,sys} <p>/</p> {lnet,lustre} <p>/mdt/lustre-MDT0000/commit_on_sharing: Found no match</p> <p>I believe the report marked as fail is correct behavior since the error happen outside of any subtest</p> <p>The issue occurred in failover configuration.</p> <p>After running replay-vbr test, the active MDS node has been changed, however, restore_lustre_params() still tries to restore the saved params on the original (now inactive) node, which causes the failure.</p> <p>I'll submit a patch.</p> <p>Patch for Lustre master branch: <a href="http://review.whamcloud.com/5628" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5628</a><br/> Patch for Lustre b2_1 branch: <a href="http://review.whamcloud.com/5627" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5627</a></p> <blockquote><p>Patch for Lustre master branch: <a href="http://review.whamcloud.com/5628" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5628</a></p></blockquote> <p>Hi Oleg, could you please land the above patch on master branch? The issue in this ticket is affecting the failover testing:<br/> <a href="https://maloo.whamcloud.com/test_sets/5a2aa132-ad66-11e2-bbea-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/5a2aa132-ad66-11e2-bbea-52540035b04c</a></p> <p>Landed for 2.1.5 and 2.4</p> Related Development Rank 1|hzve67: Rank (Obsolete) 5935 Severity