gha: cri-containerd: Add timeout to the crictl calls on testContainerStop

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 <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2023-08-15 13:04:06 +02:00
parent b29782984a
commit 84dd02e0f9

View File

@ -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