From 94c8367860e5f5e888e2827c247ee09c56890345 Mon Sep 17 00:00:00 2001 From: Jeremy Poulin Date: Mon, 13 Apr 2026 14:22:38 -0400 Subject: [PATCH] OCPEDGE-2510: fix(two-node): bump node replacement timeouts for new node installer pods Align wait windows with observed runtimes when installer pods run longer on bare-metal two-node fencing (TNF). Made-with: Cursor Agent: Auto --- test/extended/two_node/tnf_node_replacement_const.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/test/extended/two_node/tnf_node_replacement_const.go b/test/extended/two_node/tnf_node_replacement_const.go index bd0a81675d8a..509b22e395b3 100644 --- a/test/extended/two_node/tnf_node_replacement_const.go +++ b/test/extended/two_node/tnf_node_replacement_const.go @@ -189,6 +189,7 @@ const ( // Same value as ovnkubeRestartSettleWait: brief settle after Trace so installers can start before reverting to Normal. staticPodRevisionBumpSettleWait = ovnkubeRestartSettleWait // After revision bump, static-pod installers must write manifests on the replacement control-plane node. - staticPodManifestsWaitTimeout = 2 * time.Minute - staticPodManifestsPollInterval = 45 * time.Second + // CI can be slow to converge NodeInstaller; use 5m window to be generous + staticPodManifestsWaitTimeout = 5 * time.Minute + staticPodManifestsPollInterval = 30 * time.Second )