Skip to content

Commit f8ea665

Browse files
committed
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 <[email protected]>
1 parent 79e6403 commit f8ea665

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

test/e2e/deviceplugins_suite_test.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ func setupFirstNode() []byte {
108108
utils.Kubectl("node-feature-discovery", "apply", "-k", "deployments/nfd/overlays/node-feature-rules/kustomization.yaml")
109109

110110
if err = e2epod.WaitForPodsRunningReady(c, "node-feature-discovery", 2, 0,
111-
200*time.Second, map[string]string{}); err != nil {
111+
300*time.Second, map[string]string{}); err != nil {
112112
framework.Failf("unable to wait for NFD pods to be running and ready: %v", err)
113113
}
114114

0 commit comments

Comments
 (0)