From d54a139f6d55e4e2a5224ca8a40f7d2e4e7d5f62 Mon Sep 17 00:00:00 2001
From: Ed Santiago <santiago@redhat.com>
Date: Tue, 10 Oct 2017 10:22:27 -0600
Subject: [PATCH] nc (netcat): don't block when run interactively

When running the test suite interactively, "Connect to pod
hostport from the host" test hangs because nc thinks it's
got a bidirectional connection. Running with </dev/null
closes the connection after receiving the expected data,
letting the tests proceed.

This is just a suggestion for n00b-friendliness. Running
interactively is rare, but it's exactly where a n00b
will begin, and the hang costs a little time and energy
to track down.

Signed-off-by: Ed Santiago <santiago@redhat.com>
---
 test/network.bats | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/network.bats b/test/network.bats
index ea75ac37..eef4bbe0 100644
--- a/test/network.bats
+++ b/test/network.bats
@@ -159,7 +159,7 @@ function teardown() {
 	run crioctl ctr start --id "$ctr_id"
 	echo "$output"
 	[ "$status" -eq 0 ]
-	run nc -w 5 $host_ip 4888
+	run nc -w 5 $host_ip 4888 </dev/null
 	echo "$output"
 	[ "$output" = "crioctl_host" ]
 	[ "$status" -eq 0 ]