From f8ea66563e1a2753d2901de9135231e349a9340f Mon Sep 17 00:00:00 2001 From: Oleg Zhurakivskyy Date: Mon, 30 Jan 2023 17:17:55 +0200 Subject: [PATCH] e2e: Increase nfd timeout to 300 seconds Apparently some of simulated CI nodes have out of sync boot configuration. In order to be able to get the configuration in sync, the e2e NFD timeout should be increased (it takes 250-260 seconds for NFD to get up with the right boot parameters in the simulated environments). Signed-off-by: Oleg Zhurakivskyy --- test/e2e/deviceplugins_suite_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/deviceplugins_suite_test.go b/test/e2e/deviceplugins_suite_test.go index b7898e88..4d2e7bc1 100644 --- a/test/e2e/deviceplugins_suite_test.go +++ b/test/e2e/deviceplugins_suite_test.go @@ -108,7 +108,7 @@ func setupFirstNode() []byte { utils.Kubectl("node-feature-discovery", "apply", "-k", "deployments/nfd/overlays/node-feature-rules/kustomization.yaml") if err = e2epod.WaitForPodsRunningReady(c, "node-feature-discovery", 2, 0, - 200*time.Second, map[string]string{}); err != nil { + 300*time.Second, map[string]string{}); err != nil { framework.Failf("unable to wait for NFD pods to be running and ready: %v", err) }