ROSAENG-1484: Increase autonode FVT timeout to 3h

[dustman9000]

Summary

• Increase Prow step timeout for the HCP Autonode FVT job from the default 2h to 3h
• The 21 autonode test specs collectively exceed the 2h limit, causing consistent timeouts

Jira: https://redhat.atlassian.net/browse/ROSAENG-1484

Summary by CodeRabbit

This change updates the OpenShift CI configuration for the openshift-online/rosa-e2e repository to extend the Prow job timeout for the HCP Autonode FVT integration test.

What changed: The ci-operator config that defines the ocm-fvt test suite (ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-integration.yaml) adds timeout: 3h0m0s to the ocm-fvt-periodic-cs-rosa-hcp-autonode-integration-main test definition (previously subject to the default 2-hour job timeout).

Why it matters: The autonode FVT consists of 21 test specs whose combined runtime regularly exceeds the default 2-hour limit; increasing the timeout to 3 hours prevents consistent timeouts and allows the suite to complete.

Infrastructure affected: CI operator configuration for the ROSA E2E integration jobs in the OpenShift CI system—specifically the HCP Autonode FVT periodic job. No other tests or top-level configuration fields were modified.

[openshift-ci-robot]

@dustman9000: This pull request references ROSAENG-1484 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Increase Prow step timeout for the HCP Autonode FVT job from the default 2h to 3h
• The 21 autonode test specs collectively exceed the 2h limit, causing consistent timeouts

Jira: https://redhat.atlassian.net/browse/ROSAENG-1484

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

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: e6f5b742-8dbe-429c-91d7-4f31479102fb

📥 Commits

Reviewing files that changed from the base of the PR and between 2380370 and ef95df9.

📒 Files selected for processing (1)

• ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-integration.yaml

✅ Files skipped from review due to trivial changes (1)

• ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-integration.yaml

---

Walkthrough

Adds a timeout: 3h0m0s field to the ocm-fvt-periodic-cs-rosa-hcp-autonode-integration-main test entry in the ROSA HCP integration CI operator YAML.

Changes

Test Configuration Timeout Update

Layer / File(s)	Summary
Test timeout configuration ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__ocm-fvt-rosa-hcp-integration.yaml	A timeout: 3h0m0s field is added to the ocm-fvt-periodic-cs-rosa-hcp-autonode-integration-main test definition.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/release#79783: Also adds an explicit timeout: 3h0m0s to a CI operator test definition.
• openshift/release#78772: Introduced/modified the same test definition; related changes to this job's configuration.
• openshift/release#79828: Updates timeouts for e2e job/test definitions in CI configs.

Suggested labels

lgtm, approved, rehearsals-ack

Suggested reviewers

• tiwillia
• bmeng

🚥 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 clearly and specifically describes the main change: increasing the autonode FVT timeout from 2 hours to 3 hours, with a reference to the Jira ticket.
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	PR modifies only CI-operator config (timeout setting), not Ginkgo test files. Custom check for Ginkgo test name stability is not applicable to YAML configuration changes.
Test Structure And Quality	✅ Passed	PR modifies CI configuration (adding a timeout to a Prow job definition), not Ginkgo test code. The custom check for Ginkgo test structure and quality is not applicable to CI configuration files.
Microshift Test Compatibility	✅ Passed	PR does not add new Ginkgo e2e tests; it only modifies a timeout setting in a CI configuration file. The MicroShift compatibility check applies only to new e2e tests, not CI configuration changes.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR modifies only a CI operator configuration YAML file (adding a timeout setting) and does not add any new Ginkgo e2e tests, making this SNO compatibility check inapplicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only a CI test timeout setting in a Prow configuration file, not deployment manifests, operator code, or controllers. No scheduling constraints are introduced.
Ote Binary Stdout Contract	✅ Passed	PR only modifies YAML config (adds timeout), not code. OTE Binary Stdout Contract check applies only to code with stdout writes in process-level code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only a ci-operator YAML config file to set timeout, not adding any Ginkgo e2e test code. Check is not applicable to configuration-only changes.
No-Weak-Crypto	✅ Passed	PR only modifies YAML CI/CD configuration file to increase test timeout from 2h to 3h; contains no cryptographic code or weak crypto patterns.
Container-Privileges	✅ Passed	The modified file contains no privileged container settings like privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root user configuration.
No-Sensitive-Data-In-Logs	✅ Passed	PR only adds a timeout configuration parameter to a test definition; no logging code or actual sensitive data (passwords, tokens, API keys, PII) is added or exposed.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

@openshift-ci[bot]: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@dustman9000: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-online-rosa-e2e-main-ocm-fvt-rosa-hcp-integration-ocm-fvt-periodic-cs-rosa-hcp-autonode-integration-main	N/A	periodic	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[davidleerh]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davidleerh, dustman9000

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift-online/rosa-e2e/OWNERS [dustman9000]
• ci-operator/jobs/openshift-online/rosa-e2e/OWNERS [dustman9000]

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

[davidleerh]

/pj-rehearse

[openshift-merge-bot]

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

[dustman9000]

/pj-rehearse ack

[openshift-merge-bot]

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