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-2003 Lustre <p>Test conf-sanity 21d failed with </p> <p>conf-sanity test_21d: @@@@@@ FAIL: import is not in FULL state<br/> Trace dump:<br/> = ./../tests/test-framework.sh:3709:error_noexit()<br/> = ./../tests/test-framework.sh:3731:error()<br/> = ./../tests/test-framework.sh:4764:wait_osc_import_state()<br/> = ./conf-sanity.sh:721:test_21d()<br/> = ./../tests/test-framework.sh:3967:run_one()<br/> = ./../tests/test-framework.sh:3997:run_one_logged()<br/> = ./../tests/test-framework.sh:3819:run_test()<br/> = ./conf-sanity.sh:731:main()</p> MDS and MGS are the same server but two different disk are used for the MDT and MGT. LU-2003

conf-sanity 21d @@@@@@ FAIL: import is not in FULL state

Bug Minor Resolved Cannot Reproduce Jian Yu James A Simmons tests Fri, 21 Sep 2012 11:05:10 +0000 Tue, 6 Jan 2015 18:50:53 +0000 Tue, 6 Jan 2015 18:50:53 +0000 Lustre 2.3.0 Lustre 2.4.0 0 6 <p>Yujian</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>From dmesg on the OSS:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[ 1207.629766] Lustre: DEBUG MARKER: == conf-sanity test 21d: start mgs then ost and then mds == 10:53:04 (1348239184) [ 1467.507155] Lustre: DEBUG MARKER: rpc : @@@@@@ FAIL: can't put import for osc.lustre-OST0001-osc-MDT0000.ost_server_uuid into FULL state after 140 sec, have DISCONN [ 1469.733721] Lustre: DEBUG MARKER: conf-sanity test_21d: @@@@@@ FAIL: import is not in FULL state </pre> </div></div> <p>After several runs of conf-sanity and running conf-sanity test 21d alone, I'm able to reproduce this error. I have a separate but co-located MGS and MDS as in the original setup.</p> <p>Results for this failure are at <a href="https://maloo.whamcloud.com/test_sessions/cc509aae-6806-11e3-a01f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/cc509aae-6806-11e3-a01f-52540035b04c</a></p> <p>I'm sorry for the late reply. I've manually running conf-sanity test 21d alone with separate MGS and MDT on the latest master branch for more than 10 times but did not reproduce the failure. I'll do more experiments.</p> <p>Still cannot reproduce the failure on master branch (build #2052) by running conf-sanity from test 0 to 22 for more than 10 times. And also failed to reproduce the failure on Lustre 2.4.3.</p> <p>James (Simmons),</p> <p>Have you seen this error recently in your testing? I've tried over the past two days to hit this error with the latest master running conf-sanity and just conf-sanity test 21d alone and can't trigger it. As you can see, Yu, Jian can't trigger the problem either. </p> <p>If you haven't seen this error, please let me know if you are comfortable closing this ticket.</p> <p>Thanks, <br/> James (Nunez)</p> <p>Actually I haven't got around to in depth testing of 2.6 the last few months with the testing of 2.5 I have been doing. Please keep this open since I do know that for 2.4 it was failing consistently for me.</p> <p>Hello James,</p> <p>Would you like us to continue to keep this ticket open?</p> <p>Thanks,<br/> ~ jfc.</p> <p>Let me test this for b2_5 and master first.</p> <p>Hi James,</p> <p>I just ran conf-sanity test 21 for 10 times on the latest Lustre b2_5 and master builds separately. All of the test runs passed. Here are the reports:<br/> <a href="https://testing.hpdd.intel.com/test_sessions/90dfb9a2-9562-11e4-8cd1-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sessions/90dfb9a2-9562-11e4-8cd1-5254006e85c2</a> (master)<br/> <a href="https://testing.hpdd.intel.com/test_sessions/e383a284-9578-11e4-8cd1-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sessions/e383a284-9578-11e4-8cd1-5254006e85c2</a> (b2_5)</p> <p>MGS and MDS are the same node but MGT and MDT use different disk partitions.</p> <p>Just confirmed that on master this now passes. I need to now test b2_5.</p> <p>Finished testing 2.5 and the problem is gone. This ticket can be closed. </p> <p>ok - thanks James!</p> Development Rank 1|hzw02f: Rank (Obsolete) 10090 Severity