From f89120662dba26f95f2bbd519b1bdee1196eecdf Mon Sep 17 00:00:00 2001 From: Greg Kurz Date: Thu, 29 Feb 2024 15:37:53 +0100 Subject: [PATCH] tests: k8s: Wait for all pods concurrently A single invocation of `kubectl wait` can handle all pods. Signed-off-by: Greg Kurz --- .../integration/kubernetes/k8s-sandbox-vcpus-allocation.bats | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/integration/kubernetes/k8s-sandbox-vcpus-allocation.bats b/tests/integration/kubernetes/k8s-sandbox-vcpus-allocation.bats index d10ed95ce3..fd2eab4d39 100644 --- a/tests/integration/kubernetes/k8s-sandbox-vcpus-allocation.bats +++ b/tests/integration/kubernetes/k8s-sandbox-vcpus-allocation.bats @@ -21,9 +21,11 @@ setup() { # Create the pods kubectl create -f "${pod_config_dir}/pod-sandbox-vcpus-allocation.yaml" + # Wait for completion + kubectl wait --for=jsonpath='{.status.conditions[0].reason}'=PodCompleted --timeout=$timeout pod --all + # Check the pods for i in {0..2}; do - kubectl wait --for=jsonpath='{.status.conditions[0].reason}'=PodCompleted --timeout=$timeout pod ${pods[$i]} [ `kubectl logs ${pods[$i]}` -eq ${expected_vcpus[$i]} ] done }