Skip to content

fix: keep polling a resource after its fetcher failed and allow re-registering one absent from the cache - #3668

Draft
csviri wants to merge 1 commit into
nextfrom
fix/per-resource-polling-resilience
Draft

csviri wants to merge 1 commit into
nextfrom
fix/per-resource-polling-resilience

Conversation

@csviri

@csviri csviri commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

…gistering one absent from the cache

- a failing resource fetcher no longer ends the polling of that resource
- a stale scheduled entry is dropped when the primary is not in the cache, so a recreated resource can be registered again

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 29, 2026
@coderabbitai

coderabbitai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant