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> |
||
---|---|---|
.. | ||
config | ||
lib | ||
applications.sh | ||
autotest_common.sh | ||
skipped_build_files.txt | ||
skipped_tests.txt |