db43b387ba
Do not use iter_pci_class_code function in tests to iterate over NVMe drives. This function can return drives which at the moment of execution can not be whitelisted for use. This can result in test errors (such as simply bdev_nvme_attach_controller RPC command failing) or even using and deleting data from NVMe drive which was not meant to be used in tests. Fixes #1235 Change-Id: I82b9935fc88605b636c2096be6c71d4880a567c8 Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1309 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
38 lines
888 B
Bash
Executable File
38 lines
888 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
testdir=$(readlink -f $(dirname $0))
|
|
rootdir=$(readlink -f $testdir/../..)
|
|
source $rootdir/scripts/common.sh
|
|
source $rootdir/test/common/autotest_common.sh
|
|
|
|
rpc_py=$rootdir/scripts/rpc.py
|
|
|
|
bdf=$(get_first_nvme_bdf)
|
|
|
|
$rootdir/app/spdk_tgt/spdk_tgt -m 0x3 &
|
|
spdk_tgt_pid=$!
|
|
trap 'kill -9 ${spdk_tgt_pid}; exit 1' SIGINT SIGTERM EXIT
|
|
|
|
waitforlisten $spdk_tgt_pid
|
|
|
|
$rpc_py bdev_nvme_attach_controller -b Nvme0 -t PCIe -a ${bdf}
|
|
|
|
# 1) Test bdev_nvme_apply_firmware RPC
|
|
# NOTE: We don't want to do real firmware update on CI
|
|
|
|
# Make sure that used firmware file doesn't exist
|
|
if [ -f non_existing_file ]; then
|
|
exit 1
|
|
fi
|
|
|
|
# a) Try to apply firmware from non existing file
|
|
$rpc_py bdev_nvme_apply_firmware non_existing_file Nvme0n1 || rv=$?
|
|
if [ -z "$rv" ]; then
|
|
exit 1
|
|
fi
|
|
|
|
$rpc_py bdev_nvme_detach_controller Nvme0
|
|
|
|
trap - SIGINT SIGTERM EXIT
|
|
killprocess $spdk_tgt_pid
|