30ff5c6f14
The test uses bdev_crypto and NVMe/TCP devices to verify that volumes with crypto parameters are correctly attached and any errors are handled as intended. It starts up two spdk_tgt processes, one is being orchestrated by SMA and the other one acts as an NVMe-oF target. This ensures that we can verify that SMA terminates discovery service connections whenever a failure occurs during crypto setup. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I74001c256d4a05d2d8d295fb6fd8375d30ab66a1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13873 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
14 lines
427 B
Bash
Executable File
14 lines
427 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
testdir=$(readlink -f "$(dirname "$0")")
|
|
rootdir=$(readlink -f "$testdir/../..")
|
|
|
|
source "$rootdir/test/common/autotest_common.sh"
|
|
|
|
run_test "sma_nvmf_tcp" $testdir/nvmf_tcp.sh
|
|
run_test "sma_vfiouser_qemu" $testdir/vfiouser_qemu.sh
|
|
run_test "sma_plugins" $testdir/plugins.sh
|
|
run_test "sma_discovery" $testdir/discovery.sh
|
|
run_test "sma_vhost" $testdir/vhost_blk.sh
|
|
run_test "sma_crypto" $testdir/crypto.sh
|