Skip to content

Conversation

@umohnani8
Copy link
Contributor

The cleanupEphemeralBuildObjects function was experiencing intermittent timeout failures during cleanup verification, even though deletions were succeeding.

Each verification used 5-minute default timeout with 1s poll interval which could exhaust rate limits leading to the "context deadline exceeded" error.

Create a dedicated 2-minute timeout context for cleanup verification and increase poll interval from 1s to 3s to reduce API call rate which should be about 40 attempts per resource.

The cleanupEphemeralBuildObjects function was experiencing intermittent
timeout failures during cleanup verification, even though deletions
were succeeding.

Each verification used 5-minute default timeout with 1s poll interval
which could exhaust rate limits leading to the "context deadline
exceeded" error.

Create a dedicated 2-minute timeout context for cleanup verification
and increase poll interval from 1s to 3s to reduce API call rate which
should be about 40 attempts per resource.

Signed-off-by: Urvashi <[email protected]>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

The cleanupEphemeralBuildObjects function was experiencing intermittent timeout failures during cleanup verification, even though deletions were succeeding.

Each verification used 5-minute default timeout with 1s poll interval which could exhaust rate limits leading to the "context deadline exceeded" error.

Create a dedicated 2-minute timeout context for cleanup verification and increase poll interval from 1s to 3s to reduce API call rate which should be about 40 attempts per resource.

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@umohnani8
Copy link
Contributor Author

umohnani8 commented Feb 11, 2026

/verified bypass

verified by passing ocl test

@umohnani8
Copy link
Contributor Author

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

@umohnani8: The verified label has been added.

Details

In response to this:

/verified bypass

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.

@cheesesashimi
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheesesashimi, umohnani8

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:
  • OWNERS [cheesesashimi,umohnani8]

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

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

@openshift-merge-bot openshift-merge-bot bot merged commit c5acb1c into openshift:main Feb 12, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants