You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Raise obs-logging cluster claim timeout due to failures - #88431
CLO's two master e2e presubmits have been dying while queued for a cluster. e2e-pre-merge failed at claim acquisition on Oct 16 (openshift/cluster-logging-operator#3543)
and Nov 2-3 (#3564-3568, #3558), and e2e-ocp-5-0 on Nov 3 (#3565), each with:
failed to wait for the created cluster claim to become ready: timed out waiting for the condition
Standby clusters in the obs-logging pools are hibernated, so every claim
pays a resume before it is fulfilled — observed 4-11 minutes against pools
showing standby. The 1h claim timeout turns queueing behind those resumes
into job failures.
The other logging repos already run 1h30m claims against these same pools
The OpenShift CI configuration for Cluster Logging Operator increases cluster-claim timeouts for the e2e-ocp-5-0 and e2e-pre-merge presubmits from 1 hour to 1 hour 30 minutes. This gives claims more time to complete when obs-logging clusters are queued for resume.
Claims can wait longer for a cluster. No merge-blocking risk was identified.
Pre-merge checks: 14
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly describes the increase in the obs-logging cluster claim timeout.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names
The PR changes two cluster-claim timeouts. It does not add or change Ginkgo test titles.
Test Structure And Quality
The PR only increases two cluster-claim timeouts in CI configuration. It does not add or change Ginkgo test code.
Microshift Test Compatibility
The PR changes two cluster-claim timeouts in CI configuration. It adds no Ginkgo tests, so this check does not apply.
Single Node Openshift (Sno) Test Compatibility
The PR changes two cluster-claim timeouts in CI configuration. It adds no Ginkgo e2e tests, so the check does not apply.
Topology-Aware Scheduling Compatibility
The PR only increases two CI cluster-claim timeouts. It does not introduce scheduling constraints or change deployment manifests, operator code, or controllers.
Ote Binary Stdout Contract
The PR only increases two cluster-claim timeouts. It does not change OTE process-level stdout behavior.
Ipv6 And Disconnected Network Test Compatibility
The PR changes two cluster-claim timeouts. It does not add Ginkgo tests.
No-Weak-Crypto
The diff only increases two cluster claim timeouts. It does not introduce cryptography or secret comparisons.
Container-Privileges
The PR changes only two cluster-claim timeouts. It does not introduce any of the listed container privilege settings.
No-Sensitive-Data-In-Logs
The PR only increases two cluster-claim timeouts. It adds no logging that may expose sensitive data.
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.
openshift-ciBot
added
the
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
label
Nov 5, 2026
[REHEARSALNOTIFIER] @cahartma: 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:
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
approvedIndicates a PR has been approved by an approver from all required OWNERS files.lgtmIndicates that a PR is ready to be merged.rehearsals-ackSignifies that rehearsal jobs have been acknowledged
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
openshift-ci
Bot
added
the
approved
openshift-merge-bot
Bot
added
the
rehearsals-ack
Why
CLO's two master e2e presubmits have been dying while queued for a cluster.
e2e-pre-mergefailed at claim acquisition on Oct 16 (openshift/cluster-logging-operator#3543)and Nov 2-3 (#3564-3568, #3558), and
e2e-ocp-5-0on Nov 3 (#3565), each with:Standby clusters in the obs-logging pools are hibernated, so every claim
pays a resume before it is fulfilled — observed 4-11 minutes against pools
showing standby. The 1h claim timeout turns queueing behind those resumes
into job failures.
The other logging repos already run 1h30m claims against these same pools
@jcantrill @vparfonov
Summary by CodeRabbit
The OpenShift CI configuration for Cluster Logging Operator increases cluster-claim timeouts for the
e2e-ocp-5-0ande2e-pre-mergepresubmits from 1 hour to 1 hour 30 minutes. This gives claims more time to complete when obs-logging clusters are queued for resume.