There are subtle differences in the way fc is creating associations,
causing the error messages from 'nvme connect' to be different than
on other transports. As we'll get notified anyway when 'nvme connect'
fails there is not point is specifying the error message in the response
files, so just suppress error messages here.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Running nvme/041
Test unauthenticated connection (should fail)
-no controller found: failed to write to nvme-fabrics device
NQN:blktests-subsystem-1 disconnected 0 controller(s)
Test authenticated connection
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test host authentication
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test invalid ctrl authentication (should fail)
-no controller found: failed to write to nvme-fabrics device
NQN:blktests-subsystem-1 disconnected 0 controller(s)
Test valid ctrl authentication
NQN:blktests-subsystem-1 disconnected 1 controller(s)
Test invalid ctrl key (should fail)
-no controller found: failed to write to nvme-fabrics device
NQN:blktests-subsystem-1 disconnected 0 controller(s)
Test complete
if [[ -n "${ctrlkey}" ]]; then
ARGS+=(--dhchap-ctrl-secret="${ctrlkey}")
fi
- nvme connect "${ARGS[@]}"
+ nvme connect "${ARGS[@]}" 2> /dev/null
}
_nvme_discover() {