Skip both sanity test_151 and test_156 during interop testing,
since this is really testing server-side functionality only
(OSS caching behavior). And it makes sense to just exclude
test_151 and test_156 during interop testing, otherwise it
seems that the client version of the test can become
inconsistent with the caching behavior/tunables on the OSS
and the failures don't mean anything. There is enough
non-interop testing to catch any regressions in the OSS
cache behavior.
Test-Parameters: trivial
Signed-off-by: Alex Deiter <adeiter@tintri.com>
Change-Id: I39a8b54894d5b0c7573e6c56d1f8e1ba02b3e3fe
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/50777
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Jian Yu <yujian@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
test_151() {
[ $PARALLEL == "yes" ] && skip "skip parallel run"
remote_ost_nodsh && skip "remote OST with nodsh"
+ (( CLIENT_VERSION == OST1_VERSION )) ||
+ skip "LU-13081: no interop testing for OSS cache"
local CPAGES=3
local list=$(comma_list $(osts_nodes))
skip "stats not implemented on old servers"
[ "$ost1_FSTYPE" = "zfs" ] &&
skip "LU-1956/LU-2261: stats not implemented on OSD ZFS"
+ (( CLIENT_VERSION == OST1_VERSION )) ||
+ skip "LU-13081: no interop testing for OSS cache"
local CPAGES=3
local BEFORE