From 665df5794e4812e0811b21b2c561b3135aa22b12 Mon Sep 17 00:00:00 2001 From: Anish Shah Date: Fri, 12 Jul 2024 09:23:32 -0700 Subject: [PATCH] wait for pod to be ready before continuing with the test This test is flaky. I have noticed that this happens because the pod is not READY when it is being deleted at the end of the test. This fix ensures that the pod is READY before continuing with the rest of the test. --- test/e2e_node/pids_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e_node/pids_test.go b/test/e2e_node/pids_test.go index f6b5d2d448f..84a7b118d03 100644 --- a/test/e2e_node/pids_test.go +++ b/test/e2e_node/pids_test.go @@ -90,7 +90,7 @@ func makePodToVerifyPids(baseName string, pidsLimit resource.Quantity) *v1.Pod { func runPodPidsLimitTests(f *framework.Framework) { ginkgo.It("should set pids.max for Pod", func(ctx context.Context) { ginkgo.By("by creating a G pod") - pod := e2epod.NewPodClient(f).Create(ctx, &v1.Pod{ + pod := e2epod.NewPodClient(f).CreateSync(ctx, &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name: "pod" + string(uuid.NewUUID()), Namespace: f.Namespace.Name,