No-ISSUE: Increase timeout for HA ISO_NO_REGISTRY job

[pawanpinjarkar]

Summary by CodeRabbit

This PR updates OpenShift CI configuration in the openshift/release repository (nightly 5.0 ci-operator config) to set an explicit timeout for the e2e-agent-ha-dualstack-iso-no-registry-techpreview test job. The job configuration now includes timeout: 3h0m0s in ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml, ensuring the job will be terminated after three hours if it hasn't completed.

[openshift-ci-robot]

@pawanpinjarkar: This pull request explicitly references no jira issue.

Details

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

[pawanpinjarkar]

/cc @bfournie

[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: 97547b3e-787b-4f86-9edb-3559cf05339a

📥 Commits

Reviewing files that changed from the base of the PR and between 8be3b25 and 9c81226.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/release/openshift-release-main-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml

---

Walkthrough

A single timeout: 3h0m0s field is added to the e2e-agent-ha-dualstack-iso-no-registry-techpreview job in the nightly-5.0 CI configuration.

Changes

CI Job Timeout Configuration

Layer / File(s)	Summary
e2e test job timeout setting ci-operator/config/openshift/release/openshift-release-main__nightly-5.0.yaml	The e2e-agent-ha-dualstack-iso-no-registry-techpreview job gains timeout: 3h0m0s.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 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 timeout for a specific test job (HA ISO_NO_REGISTRY). It directly matches the changeset which adds a 3h0m0s timeout to the e2e-agent-ha-dualstack-iso-no-registry-techpreview job configuration.
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	This PR modifies only YAML CI operator configuration files, not Ginkgo test code. The custom check for stable test names does not apply to non-Go configuration files.
Test Structure And Quality	✅ Passed	Custom check for Ginkgo test structure is not applicable; PR only modifies YAML CI configuration, not test code.
Microshift Test Compatibility	✅ Passed	PR only modifies CI configuration YAML to update a test job timeout; no new Ginkgo e2e test code is added, so MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI operator configuration (timeout value) for an existing test job, not adding any new Ginkgo e2e tests. The SNO compatibility check only applies when new tests are added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only a CI test job timeout in a ci-operator config file, not deployment manifests, operator code, or controllers with scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	PR only modifies YAML CI config to add test timeout; no executable code changes that could violate OTE Binary Stdout Contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only CI YAML configuration files to increase timeout. No new Ginkgo e2e test code is added, so the check does not apply.
No-Weak-Crypto	✅ Passed	PR only adds timeout configuration to YAML CI job; no weak crypto algorithms (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB), custom crypto implementations, or secret comparisons detected.
Container-Privileges	✅ Passed	PR modifies only a timeout value for a CI test job; contains no changes to container privileges, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or runAsUser settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR change adds only a timeout duration (3h0m0s) to a CI test job config. No sensitive data, logging of credentials, or PII exposure detected.

_{✏️ 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]

[REHEARSALNOTIFIER]
@pawanpinjarkar: 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-release-main-nightly-5.0-e2e-agent-ha-dualstack-iso-no-registry-techpreview	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.

[bfournie]

/lgtm

[bfournie]

/approve

[xueqzhan]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie, pawanpinjarkar, xueqzhan

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/release/OWNERS [xueqzhan]
• ci-operator/jobs/openshift/release/OWNERS [xueqzhan]

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

[pawanpinjarkar]

/pj-rehearse ack

[openshift-merge-bot]

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

[openshift-ci]

@pawanpinjarkar: 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.