From 17ecb9f74035340c66553497b122fe6d0e901077 Mon Sep 17 00:00:00 2001 From: Ashutosh Kumar Date: Thu, 29 Sep 2022 21:13:56 +0530 Subject: [PATCH] use correct timeout for pod startup wait Signed-off-by: Ashutosh Kumar --- test/e2e/storage/non_graceful_node_shutdown.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/storage/non_graceful_node_shutdown.go b/test/e2e/storage/non_graceful_node_shutdown.go index 558377d5a0d..c9dbb6a0889 100644 --- a/test/e2e/storage/non_graceful_node_shutdown.go +++ b/test/e2e/storage/non_graceful_node_shutdown.go @@ -118,7 +118,7 @@ var _ = utils.SIGDescribe("[Feature:NodeOutOfServiceVolumeDetach] [Disruptive] [ LabelSelector: labelSelectorStr, FieldSelector: fields.OneTermNotEqualSelector("spec.nodeName", oldNodeName).String(), } - _, err = e2epod.WaitForAllPodsCondition(c, ns, podListOpts, 1, "running and ready", framework.PodListTimeout, testutils.PodRunningReady) + _, err = e2epod.WaitForAllPodsCondition(c, ns, podListOpts, 1, "running and ready", framework.PodStartTimeout, testutils.PodRunningReady) framework.ExpectNoError(err) // Bring the node back online and remove the taint