Increase OCM FVT job timeouts to 3h - #80062
Conversation
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent)
|
@redhat-chai-bot: GitHub didn't allow me to request PR reviews from the following users: openshift-online. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
openshift-ci
Bot
added
the
needs-ok-to-test
|
Hi @redhat-chai-bot. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
WalkthroughThis PR adds explicit 3-hour timeout ( ChangesROSA E2E Periodic Test Job Timeouts
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
/lgtm |
|
[REHEARSALNOTIFIER]
A total of 28 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/ok-to-test |
openshift-ci
Bot
added
ok-to-test
|
@redhat-chai-bot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/pj-rehearse periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-rosa-classic-staging-ocm-fvt-periodic-cs-osd-rh-aws-staging-main |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-rosa-hcp-integration-ocm-fvt-periodic-cs-rosa-hcp-backup-restore-integration-main |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/approve |
|
@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidleerh, dustman9000, redhat-chai-bot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
|
/unhold |
openshift-ci
Bot
removed
the
do-not-merge/hold
bf448fe
into
openshift:main
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
Add timeout: 3h0m0s to all 29 OCM FVT periodic test entries across all 5 config variants (HCP staging/integration, Classic staging/integration, OSD GCP staging). The autonode integration job already had a 3h timeout (PR openshift#79932); this extends the same timeout to all remaining OCM FVT jobs to prevent Prow-level timeouts when ginkgo test suite timeouts have been increased. References: PR openshift#79932 (Autonode FVT timeout precedent) Co-authored-by: Chai Bot <chai-bot@redhat.com>
4 participants
Add
timeout: 3h0m0sto all OCM FVT periodic test entries across all 5 config variants:ocm-fvt-rosa-hcp-staging(13 jobs)ocm-fvt-rosa-classic-staging(8 jobs)ocm-fvt-osd-gcp-staging(4 jobs)ocm-fvt-rosa-hcp-integration(2 jobs — autonode already had 3h)ocm-fvt-rosa-classic-integration(1 job)Context
Ginkgo test suite timeouts were recently increased (HCP cluster readiness: 20min → 30min, test suites: up to 3h). The Prow job-level timeout needs to accommodate these longer test durations to prevent premature job termination.
Precedent: PR #79932 set 3h timeout for the autonode integration job (ROSAENG-1484). This PR extends the same timeout to all remaining OCM FVT jobs.
Generated files updated via
make jobs./cc @openshift-online
Summary by CodeRabbit
This PR increases the job-level timeout to 3 hours for OCM (OpenShift Container Management) FVT (Functional Verification Testing) periodic jobs across five configuration variants in the OpenShift Online ROSA E2E test suite. The timeout changes prevent Prow from prematurely terminating these jobs, as the underlying Ginkgo test suites have been extended to run up to 3 hours (including HCP cluster readiness checks extended from 20m to 30m).
Impact across variants:
autonodejob already had a 3h timeout from prior changes)The configuration changes are minimal and surgical—only the
timeout: 3h0m0sfield is added to each affected test job definition in their respective YAML configuration files. The PR follows established precedent from earlier Prow timeout increases and the changes were generated via the repository'smake jobstooling.