[LU-2527] Interop 2.1.3<->2.4 Failure on test suite sanity test_183: ls succeeded, should have failed Created: 26/Dec/12  Updated: 21/Nov/19  Resolved: 10/Aug/13

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.0
Fix Version/s: Lustre 2.4.1, Lustre 2.5.0

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Jian Yu
Resolution: Fixed Votes: 0
Labels: None
Environment:

server: 2.1.3 RHEL6
client lustre-master tag-2.3.57


Severity: 3
Rank (Obsolete): 5946

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/bf17974e-4a83-11e2-8a7b-52540035b04c.

The sub-test test_183 failed with the following error:

ls succeeded, should have failed

== sanity test 183: No crash or request leak in case of strange dispositions ========== 23:01:24 (1355900484)
CMD: client-20-ib /usr/sbin/lctl set_param fail_loc=0x148
fail_loc=0x148
total 1
-rw-r--r-- 1 root root 4 Dec 18 23:01 f.sanity.183
 sanity test_183: @@@@@@ FAIL: ls succeeded, should have failed 


 Comments   
Comment by Sarah Liu [ 15/Jan/13 ]

Also seen in interop between 2.1.4 server and 2.4 client:
https://maloo.whamcloud.com/test_sets/e034926a-5f19-11e2-b507-52540035b04c

Comment by Jian Yu [ 16/Jul/13 ]

Patch for Lustre master branch: http://review.whamcloud.com/6994. The patch is also needed to be cherry-picked to Lustre b2_4 branch.

Comment by Jian Yu [ 10/Aug/13 ]

Patch was landed on Lustre b2_4 and master branches.

Generated at Sat Feb 10 01:25:57 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.