nvme tests should use nvme_trtype when setting up passthru target

No matter what was passed in with nvme_trtype, the target was being
set up with trtype as "loop".  This caused several passthru tests
to fail when testing tcp or rdma.

Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
Signed-off-by: Alan Adamson <alan.adamson@oracle.com>

diff --git a/tests/nvme/rc b/tests/nvme/rc
index 1c27cdee1b5f7318213a6fc480ba74d6fdcb0990..3c38408a0bfe3808c9250887a607c068196c0d86 100644 (file)
--- a/tests/nvme/rc
+++ b/tests/nvme/rc
@@ -335,7 +335,7 @@ _nvmet_passthru_target_setup() {
        local subsys_name=$1
 
        _create_nvmet_passthru "${subsys_name}"
-       port="$(_create_nvmet_port "loop")"
+       port="$(_create_nvmet_port "${nvme_trtype}")"
        _add_nvmet_subsys_to_port "${port}" "${subsys_name}"
 
        echo "$port"