From 3f6a4c2c53f8829f1394e60ece6bc03a37347e29 Mon Sep 17 00:00:00 2001 From: davdhacs <105243888+davdhacs@users.noreply.github.com> Date: Thu, 11 Jun 2026 20:54:24 -0600 Subject: [PATCH] stackrox: Add 3h timeout to ocp-4-create step The ocp-4-create step had no explicit timeout, inheriting the 2h default from the Prow entrypoint. When the first provisioning attempt fails and the retry script starts a second attempt, 2h is not enough for two full OCP provisioning cycles. This caused nightly UI E2E tests to be killed mid-provisioning on the retry. 3h accommodates two full provisioning cycles comfortably. Partially generated by AI. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../stackrox-automation-flavors-ocp-4-e2e-workflow.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml b/ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml index b8a10d37119f0..844cca09c2998 100644 --- a/ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml +++ b/ci-operator/step-registry/stackrox/automation-flavors/ocp-4-e2e/stackrox-automation-flavors-ocp-4-e2e-workflow.yaml @@ -28,6 +28,7 @@ workflow: requests: cpu: 2000m memory: 4000Mi + timeout: 3h0m0s test: - ref: stackrox-stackrox-e2e-test post: