From b7208b3c6c62d783aa3787a894e53147afaf36da Mon Sep 17 00:00:00 2001 From: Snir Sheriber Date: Wed, 24 Mar 2021 17:52:51 +0200 Subject: [PATCH] runtime: increase dial timeout On some setups, starting multiple kata pods (qemu) simultaneously on the same node might cause kata VMs booting time to increase and the pods to fail with: Failed to check if grpc server is working: rpc error: code = DeadlineExceeded desc = timed out connecting to vsock 1358662990:1024: unknown Increasing default dialing timeout to 30s should cover most cases. Signed-off-by: Snir Sheriber Fixes: #1543 (backport https://github.com/kata-containers/kata-containers/pull/1544) --- src/runtime/virtcontainers/pkg/agent/protocols/client/client.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go b/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go index db6a4f1123..a2a1a8659b 100644 --- a/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go +++ b/src/runtime/virtcontainers/pkg/agent/protocols/client/client.go @@ -35,7 +35,7 @@ const ( MockHybridVSockScheme = "mock" ) -var defaultDialTimeout = 15 * time.Second +var defaultDialTimeout = 30 * time.Second var defaultCloseTimeout = 5 * time.Second var hybridVSockPort uint32