The output of _nvme_discover() will be changed according to
${nvme_trtype} and the number of NICs. For example: nvme/033
with nvme_trtype=tcp and two NICs got the following error:
------------------------------------------------
Running nvme/033
-Discovery Log Number of Records 1, Generation counter X
+Discovery Log Number of Records 2, Generation counter X
=====Discovery Log Entry 0======
-trtype: loop
+trtype: tcp
+subnqn: nqn.2014-08.org.nvmexpress.discovery
+=====Discovery Log Entry 1======
+trtype: tcp
subnqn: blktests-subsystem-1
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test complete
------------------------------------------------
Remove volatile output to fix the issue.
Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
_setup_nvmet
port=$(_nvmet_passthru_target_setup "${subsys}")
- _nvme_discover "${nvme_trtype}" | _filter_discovery
-
nsdev=$(_nvmet_passthru_target_connect "${nvme_trtype}" "${subsys}")
compare_dev_info "${nsdev}"
Running nvme/033
-Discovery Log Number of Records 1, Generation counter X
-=====Discovery Log Entry 0======
-trtype: loop
-subnqn: blktests-subsystem-1
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test complete