stackrox: Add 3h timeout to ocp-4-create step

[davdhacs]

Summary

The ocp-4-create step in the stackrox-automation-flavors-ocp-4-e2e workflow had no explicit timeout, inheriting the default 2h from the Prow entrypoint. When the first OCP provisioning attempt fails (transient GCP/bootstrap flake) and the retry script starts a second attempt, 2h is not enough for two full provisioning cycles. This caused the nightly OCP 4.22 UI E2E job to be killed mid-provisioning on the retry (build 2064515097526538240).

• Add timeout: 3h0m0s to the ocp-4-create step to fit two full provisioning cycles
• The ocp-4-destroy step already had an explicit timeout: 30m0s

/uncc
/hold

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 80069749-b0d4-4dba-8256-f45667b2cdee

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ocp4-create-timeout

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[davdhacs]

Superseded by openshift#80452