Skip to content

[release-4.22] OCPBUGS-112554: Use Add() instead of AddRateLimited() for routine Profile enqueues - #1601

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-1595-to-release-4.22
Aug 26, 2026
Merged

[release-4.22] OCPBUGS-112554: Use Add() instead of AddRateLimited() for routine Profile enqueues#1601
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-1595-to-release-4.22

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1595

/assign jmencak

Change 1:

workqueue.DefaultTypedControllerRateLimiter's AddRateLimited() draws from
a single 10qps/burst-100 token bucket shared by every item in the queue,
regardless of kind or key.  Cascade/trigger enqueues (Pod/Node change to
Profile update, per-Profile bootstrap loop, initial bootstrap event)
used AddRateLimited() for ordinary enqueuing rather than error retries.
During a burst of ~100 nodes joining, this exhausted the shared bucket,
delaying later Profile syncs by minutes even though they were never dropped,
just queued behind the backlog.

Switch these call sites to Add(), which is unthrottled and still deduped
by key via the delaying queue's dirty set.  Keep AddRateLimited() only for
its intended purpose: the retry-after- sync()-error path, where per-key
exponential backoff is correct.

Change 2:

validateTunedCRs() called UpdateStatus() on every Tuned CR on every invocation,
even when the computed status conditions were identical to what's already
stored.  Compare the newly computed status against the cached copy with
reflect.DeepEqual() and skip the UpdateStatus() call when nothing semantically
changed.

Resolves: OCPBUGS-105458
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ac7d157c-f759-4a5f-9c04-76923d143155

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@openshift-ci
openshift-ci Bot requested review from ffromani and swatisehgal August 21, 2026 11:55
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-112279 has been cloned as Jira Issue OCPBUGS-112554. Will retitle bug to link to clone.
/retitle [release-4.22] OCPBUGS-112554: Use Add() instead of AddRateLimited() for routine Profile enqueues

Details

In response to this:

This is an automated cherry-pick of #1595

/assign jmencak

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 changed the title [release-4.22] OCPBUGS-112279: Use Add() instead of AddRateLimited() for routine Profile enqueues [release-4.22] OCPBUGS-112554: Use Add() instead of AddRateLimited() for routine Profile enqueues Aug 21, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Aug 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-112554, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-112279 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-112279 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
  • bug has dependents

Requesting review from QA contact:
/cc @shyadav10

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1595

/assign jmencak

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-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 21, 2026
@openshift-ci
openshift-ci Bot requested a review from shyadav10 August 21, 2026 11:56
@jmencak

jmencak commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-techpreview
/test e2e-gcp-pao
/test e2e-gcp-pao-updating-profile
/test e2e-gcp-pao-workloadhints
/test e2e-hypershift
/test e2e-hypershift-pao
/test e2e-no-cluster
/test e2e-upgrade

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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.

@jmencak

jmencak commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/approve
/label backport-risk-assessed
/verified later @shyadav10

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@jmencak: Only users can be targets for the /verified later command.

Details

In response to this:

/approve
/label backport-risk-assessed
/verified later by @shyadav10

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 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 26, 2026
@jmencak

jmencak commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/verified later @shyadav10

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Aug 26, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@jmencak: This PR has been marked to be verified later by @shyadav10.

Details

In response to this:

/verified later @shyadav10

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 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, openshift-cherrypick-robot

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit a3edd3e into openshift:release-4.22 Aug 26, 2026
19 checks passed
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-112554: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-112554 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #1595

/assign jmencak

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.

@jmencak

jmencak commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/cherry-pick release-4.21

@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@jmencak: new pull request created: #1616

Details

In response to this:

/cherry-pick release-4.21

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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 verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants