[LU-7757] Interop master<->2.7.1 - sanity-sec test_24: proc readable file read failed Created: 08/Feb/16  Updated: 09/May/18  Resolved: 09/May/18

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.8.0, Lustre 2.10.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Sarah Liu
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

2.7.1 Server/EL7 Client
b2_7_fe/34, master - build# 3316


Issue Links:
Related
is related to LU-5030 "lctl {get,set}_param" should also ch... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Saurabh Tandan <saurabh.tandan@intel.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/97ce8a68-ccde-11e5-8b0e-5254006e85c2.

The sub-test test_24 failed with the following error:

proc readable file read failed

test log:

CMD: shadow-4vm12 /usr/sbin/lctl list_nids | grep tcp | cut -f 1 -d '@'
CMD: shadow-4vm11,shadow-4vm12 /usr/sbin/lctl get_param -R nodemap
shadow-4vm12: get_param: invalid option -- 'R'
shadow-4vm12: get the Lustre or LNET parameter
shadow-4vm12: usage: get_param [-n|-N|-F] <param_path1 param_path2 ...>
shadow-4vm12: Get the value of Lustre or LNET parameter from the specified path.
shadow-4vm12: The path can contain shell-style filename patterns.
shadow-4vm12:   -n  Print only the value and not parameter name.
shadow-4vm12:   -N  Print only matched parameter names and not the values.
shadow-4vm12:       (Especially useful when using patterns.)
shadow-4vm12:   -F  When -N specified, add '/', '@' or '=' for directories,
shadow-4vm12:       symlinks and writeable files, respectively.
shadow-4vm11: get_param: invalid option -- 'R'
shadow-4vm11: get the Lustre or LNET parameter
shadow-4vm11: usage: get_param [-n|-N|-F] <param_path1 param_path2 ...>
shadow-4vm11: Get the value of Lustre or LNET parameter from the specified path.
shadow-4vm11: The path can contain shell-style filename patterns.
shadow-4vm11:   -n  Print only the value and not parameter name.
shadow-4vm11:   -N  Print only matched parameter names and not the values.
shadow-4vm11:       (Especially useful when using patterns.)
shadow-4vm11:   -F  When -N specified, add '/', '@' or '=' for directories,
shadow-4vm11:       symlinks and writeable files, respectively.
 sanity-sec test_24: @@@@@@ FAIL: proc readable file read failed 


 Comments   
Comment by Andreas Dilger [ 09/Feb/16 ]

Are the client nodes running different versions of Lustre? The "get_param -R" option was just added in master, but since the test script is running only on the client node then it shouldn't need interop for this option?

In any case this is a harmless error in the test script, but it would be good to fix it in master before release so that it doesn't cause continuous interop test failures.

Comment by Saurabh Tandan (Inactive) [ 10/Feb/16 ]

Another instance found for interop tag 2.7.66 - 2.7.1 Server/EL7 Client, build# 3316
https://testing.hpdd.intel.com/test_sets/97ce8a68-ccde-11e5-8b0e-5254006e85c2

Another instance found for interop tag 2.7.66 - 2.7.1 Server/EL6.7 Client, build# 3316
https://testing.hpdd.intel.com/test_sets/f4362f32-ccdd-11e5-b80c-5254006e85c2

Comment by Saurabh Tandan (Inactive) [ 24/Feb/16 ]

Another instance found for interop - 2.7.1 Server/EL7 Client, tag 2.7.90.
https://testing.hpdd.intel.com/test_sessions/3b9722f8-d2f8-11e5-bf08-5254006e85c2
Another instance found for interop - 2.7.1 Server/EL6.7 Client, tag 2.7.90.
https://testing.hpdd.intel.com/test_sessions/f371534e-d573-11e5-bc47-5254006e85c2

Comment by Sarah Liu [ 18/Mar/16 ]

the "-R" option was added by LU-5030, landed on tag-2.8.50. need check the server version, if older than that, remove the option "-R"

Comment by Gerrit Updater [ 01/Apr/16 ]

Wei Liu (wei3.liu@intel.com) uploaded a new patch: http://review.whamcloud.com/19303
Subject: LU-7757 test: sanity-sec test_24 add version check
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: af481c86ba47e8dc23cdffbbc27b7f90cb98f9e1

Comment by Sarah Liu [ 09/May/18 ]

This issue has been fixed by adding nodemap supportive check. cannot reproduce in master and b2_10

Generated at Sat Feb 10 02:11:40 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.