From 535e22e5f89757855785f9e7129bb44514bb8688 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Thu, 18 May 2017 14:44:02 +0000 Subject: [PATCH] Wait for nodes to be ready before starting pods Otherwise we can schedule all pods on the same node, which isn't such a good test --- test/840_weave_kube_3_test.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/test/840_weave_kube_3_test.sh b/test/840_weave_kube_3_test.sh index 6b39d756..4e4fef80 100755 --- a/test/840_weave_kube_3_test.sh +++ b/test/840_weave_kube_3_test.sh @@ -64,6 +64,12 @@ assert "run_on $HOST1 ps aux | grep -c '[d]efunct'" "0" assert "run_on $HOST2 ps aux | grep -c '[d]efunct'" "0" assert "run_on $HOST3 ps aux | grep -c '[d]efunct'" "0" +check_ready() { + run_on $HOST1 "$KUBECTL get nodes | grep -c -w Ready | grep $NUM_HOSTS" +} + +assert_raises 'wait_for_x check_ready "hosts to be ready"' + # See if we can get some pods running that connect to the network run_on $HOST1 "$KUBECTL run --image-pull-policy=Never nettest --image=$IMAGE --replicas=3 -- -peers=3 -dns-name=nettest.default.svc.cluster.local." # Create a headless service so they can be found in Kubernetes DNS