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-1193 Lustre <p>When running conf-sanity.sh with 2.1 server and 2.2 client, sub-test 61 failed, since the test script is different between server and client. It actually ran the client script on the server side which caused error. After copying conf-sanity from server to client, the test passed. The similar issue also found in some sanity sub-tests, such as 133a,133d,160</p> LU-1193

test script incompatibility when running server as 2.1 and client as 2.2

Bug Minor Resolved Fixed Yang Sheng Sarah Liu Tue, 6 Mar 2012 23:11:13 +0000 Fri, 25 May 2012 18:40:04 +0000 Tue, 8 May 2012 00:56:49 +0000 Lustre 2.3.0 0 2 <p>Yangsheng</p> <p>Could you please look into this one?</p> <p>THanks</p> <p>Peter</p> <p>This is causing many tests (14% or more) to fail during autotest. It makes sense to add a simple check to each of the failing subtests to verify whether the server is capable of running this test properly.</p> <p>The easiest way would be something like "do_facet mds lctl get_param version" and check if it is new enough. </p> <p>A better solution would be to have a test-specific check, like for sanity test_133d to see if the MDS has the right proc stats or not. In other cases it might not be so easy and a version check may be needed. </p> <p>Ok, So we have a list as below:</p> <p>conf-sanity-61<br/> sanity-133a,133d,160</p> <p>Please comment other if not in the list.</p> <p>sanity-225a sanity-225b, these two tests should not be run on 2.1.x, it will cause oops.</p> <p>recovery-small, subtest 100 to 105 are new in 2.2 script, should not be run under 2.1</p> <p>Yang Sheng,<br/> having a list is the starting point, but what still needs to be done is to fix the test scripts so that they are skipped if the server does not have the right functionality to run the test from the client. This can be checked at the start of these failing tests by looking at "lctl get_param mdc.*.connect_flags" (for features that have a connect flag) or by "do_facet $SINGLEMDS </p> {some check} <p>" for other features. The check might be looking at the presence of "lctl list_param mdt.*.rename_stats" for sanity.sh test_133d, or simply "lctl get_param version" for others.</p> <p>Having just a list of failing tests here in Jira does not stop those tests from failing, and it pollutes the test results with failures, which wastes everyone's time.</p> <p>Yang Sheng,</p> <p>Could you create a new ticket for each of these tests, or possibly groups of tests. We don't group source code issues like this and shouldn't do so with test code issues either.</p> <p>Thanks</p> <p>Chris</p> <p>Close it, please reopen if any works need.</p> Related LU-1209 LU-664 Development Rank 1|hzv4dz: Rank (Obsolete) 4244 Severity