From 84dd02e0f9baf942181d2808fc3f31c1077a0ebd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Tue, 15 Aug 2023 13:04:06 +0200 Subject: [PATCH] gha: cri-containerd: Add timeout to the crictl calls on testContainerStop MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit As part of the runners, we're hitting a timeout that I cannot reproduce, at all, when allocating the same instance and running the tests manually. The default timeout to connect to the server is 2s when using `crictl`. Let's increase this to 20s. It's fairly important to mention that in the first tests I used a timeout of 10s, and that helped but we still hit issues every now and then. Signed-off-by: Fabiano Fidêncio --- tests/integration/cri-containerd/integration-tests.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/integration/cri-containerd/integration-tests.sh b/tests/integration/cri-containerd/integration-tests.sh index d9919bb68c..33f212856c 100755 --- a/tests/integration/cri-containerd/integration-tests.sh +++ b/tests/integration/cri-containerd/integration-tests.sh @@ -204,11 +204,11 @@ EOF function testContainerStop() { info "show pod $podid" - sudo crictl pods --id $podid + sudo crictl --timeout=20s pods --id $podid info "stop pod $podid" - sudo crictl stopp $podid + sudo crictl --timeout=20s stopp $podid info "remove pod $podid" - sudo crictl rmp $podid + sudo crictl --timeout=20s rmp $podid sudo cp "$default_containerd_config_backup" "$default_containerd_config" restart_containerd_service