Skip to content

ROSA CI: Increase E2E job timeout from 4h to 5h#82092

Open
redhat-chai-bot wants to merge 2 commits into
openshift:mainfrom
redhat-chai-bot:rosa-ci-timeout-5h
Open

ROSA CI: Increase E2E job timeout from 4h to 5h#82092
redhat-chai-bot wants to merge 2 commits into
openshift:mainfrom
redhat-chai-bot:rosa-ci-timeout-5h

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Increase the timeout for all ROSA CLI E2E periodic and presubmit jobs from the default 4h to 5h.

Details

  • 41 timeout failures across 24 distinct ROSA E2E jobs were observed in the past week
  • Jobs consistently run out of time before test execution completes, preventing result capture
  • This change adds explicit timeout: 5h0m0s to all 20 periodic test definitions and 5 presubmit test definitions that lacked an explicit timeout
  • 2 presubmit tests that already had timeout: 6h0m0s were left unchanged
  • Job files regenerated via make ci-operator-prowgen and make sanitize-prow-jobs

Files Changed

  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml — 20 timeout additions
  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e-presubmits.yaml — 5 timeout additions
  • Regenerated job files in ci-operator/jobs/openshift/rosa/

@dustman9000 requested in Slack thread

Summary by CodeRabbit

  • Extends ROSA CLI E2E periodic and presubmit job timeouts to 5 hours to accommodate longer-running tests.
  • Applies the change to 20 periodic and 5 presubmit definitions; existing 6-hour presubmit timeouts remain unchanged.
  • Regenerates and sanitizes the corresponding Prow job files.

redhat-chai-bot and others added 2 commits July 17, 2026 16:40
The default Prow job timeout of 4h is insufficient for ROSA e2e tests
which include cluster provisioning, readiness checks, full test suite
execution, and teardown. This causes ~24 periodic jobs to fail with
timeout before tests complete.

Add explicit timeout: 5h0m0s to all 20 periodic e2e test definitions
in the e2e variant and 5 presubmit tests that were missing timeouts.
The 2 presubmit tests that already had 6h0m0s are left unchanged.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Regenerated from config changes via make ci-operator-prowgen and
make sanitize-prow-jobs. Adds timeout: 5h0m0s to decoration_config
for all ROSA e2e periodic and presubmit jobs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: e90b9d30-b2ce-4797-a29f-a1445ae17f27

📥 Commits

Reviewing files that changed from the base of the PR and between 18cd65f and 51de8d7.

⛔ Files ignored due to path filters (2)
  • ci-operator/jobs/openshift/rosa/openshift-rosa-master-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/rosa/openshift-rosa-master-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e-presubmits.yaml
  • ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml

Walkthrough

ROSA E2E presubmit and job configurations add explicit 5h0m0s timeouts to 25 job entries without changing other shown configuration fields.

Changes

ROSA E2E timeout configuration

Layer / File(s) Summary
Presubmit job timeouts
ci-operator/config/openshift/rosa/openshift-rosa-master__e2e-presubmits.yaml
Five ROSA pull request jobs add timeout: 5h0m0s.
E2E job timeouts
ci-operator/config/openshift/rosa/openshift-rosa-master__e2e.yaml
Twenty ROSA E2E job entries add timeout: 5h0m0s.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: olucasfreitas, prucek

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: increasing ROSA E2E job timeouts from 4 hours to 5 hours.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Only Prow job YAML timeout fields changed; no Ginkgo titles or test code were modified, so the stability rule isn’t implicated.
Test Structure And Quality ✅ Passed PR only updates generated CI job YAML timeouts; no Ginkgo tests or assertions were changed, so the test-structure checklist is not applicable.
Microshift Test Compatibility ✅ Passed Only Prow job YAML timeout fields changed; no new Ginkgo tests or API usage were added, so MicroShift compatibility is not implicated.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only updates generated Prow YAML timeout fields; no new or modified Ginkgo tests were added.
Topology-Aware Scheduling Compatibility ✅ Passed Diff only adds timeout: 5h0m0s to ROSA ci-operator job YAMLs; no deployment, controller, or scheduling fields changed.
Ote Binary Stdout Contract ✅ Passed PR only updates generated job YAML timeouts; no main/init/TestMain/suite code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS: The PR only updates ci-operator job YAML timeouts; no new Ginkgo test bodies or network/IP-handling code were added.
No-Weak-Crypto ✅ Passed Diff only adds timeout: 5h0m0s to generated Prow YAML; no MD5/SHA1/DES/RC4/ECB, custom crypto, or secret comparisons were introduced.
Container-Privileges ✅ Passed Diff only adds timeout: 5h0m0s lines in generated job YAML; no privileged, hostPID/hostNetwork/hostIPC, SYS_ADMIN, or allowPrivilegeEscalation changes found.
No-Sensitive-Data-In-Logs ✅ Passed PASS: The PR only adds timeout fields to Prow job YAMLs; no new logging statements or secret/PII-bearing values were introduced.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@dustman9000

Copy link
Copy Markdown
Member

/lgtm
/approve
/pj-rehearse ack

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2026
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dustman9000, redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign marcolan018 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 17, 2026
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants