Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #9481

/assign haircommander

None

A prior patch addressing race conditions in this code section was
incomplete as it used 2 different locks for irqbalance and irq SMP
affinity files. This still allowed for a race condition wrt irqbalance
configuration. This fix addresses this issue by using a single lock and
by making the entire change atomic.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
Add unit tests for irq smp affinity settings. In order to do so, add
service and command manager structures that can be mocked.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
Having IRQ balancing logic inside the PreStop hook can cause issues with
ordering (possibility to hit sequence container add, replacement
container add, container stop). Moving the same logic into PostStop will
guarantee correct ordering.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
Signed-off-by: Andreas Karis <ak.karis@gmail.com>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-59403 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

/retitle [release-1.33] : : HighPerformanceHooks: Atomic locking and fix container replacement race conditions

In response to this:

This is an automated cherry-pick of #9481

/assign haircommander

None

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 release-note-none Denotes a PR that doesn't merit a release note. label Oct 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 2, 2025
@openshift-ci openshift-ci bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Oct 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 2, 2025
@openshift-ci-robot
Copy link

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-59403, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • expected Jira Issue OCPBUGS-59403 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-59403 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

/retitle [release-1.33] : : HighPerformanceHooks: Atomic locking and fix container replacement race conditions

In response to this:

This is an automated cherry-pick of #9481

/assign haircommander

None

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.

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-1.33] : OCPBUGS-59403: HighPerformanceHooks: Atomic locking and fix container replacement race conditions [release-1.33] : : HighPerformanceHooks: Atomic locking and fix container replacement race conditions Oct 2, 2025
@openshift-ci openshift-ci bot requested review from hasan4791 and QiWang19 October 2, 2025 02:23
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 2, 2025
Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign giuseppe for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #9481

/assign haircommander

None

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.

Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-ovn 97138f9 link true /test e2e-gcp-ovn

Full PR test history. Your PR dashboard.

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.

Copy link

codecov bot commented Oct 2, 2025

Codecov Report

❌ Patch coverage is 66.66667% with 29 lines in your changes missing coverage. Please review.
✅ Project coverage is 47.73%. Comparing base (29ddd0a) to head (97138f9).

Additional details and impacted files
@@               Coverage Diff                @@
##           release-1.33    #9491      +/-   ##
================================================
+ Coverage         47.65%   47.73%   +0.08%     
================================================
  Files               164      164              
  Lines             24222    24264      +42     
================================================
+ Hits              11542    11583      +41     
- Misses            11542    11543       +1     
  Partials           1138     1138              
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@andreaskaris
Copy link
Contributor

/retitle [release-1.33]:OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions

Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@andreaskaris: Re-titling can only be requested by trusted users, like repository collaborators.

In response to this:

/retitle [release-1.33]:OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions

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.

@andreaskaris
Copy link
Contributor

/retitle [release-1.33]: OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions

Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@andreaskaris: Re-titling can only be requested by trusted users, like repository collaborators.

In response to this:

/retitle [release-1.33]: OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions

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.

@andreaskaris
Copy link
Contributor

andreaskaris commented Oct 2, 2025

@haircommander this one should be retitled to
/retitle [release-1.33]: OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions
as a Jira already exists: https://issues.redhat.com/browse/OCPBUGS-59321

The follow-ups then were slightly conflicting and also contain the prior commit and are here:
4.19: https://issues.redhat.com/browse/OCPBUGS-59415 -> #9350
4.18: https://issues.redhat.com/browse/OCPBUGS-59416 -> #9351

Copy link
Contributor

openshift-ci bot commented Oct 2, 2025

@andreaskaris: Re-titling can only be requested by trusted users, like repository collaborators.

In response to this:

@haircommander this one should be retitled to
/retitle [release-1.33]: OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions
as a Jira already exists: https://issues.redhat.com/browse/OCPBUGS-59321

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.

@haircommander haircommander changed the title [release-1.33] : : HighPerformanceHooks: Atomic locking and fix container replacement race conditions [release-1.33] OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions Oct 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Oct 2, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-59321, which is invalid:

  • expected dependent Jira Issue OCPBUGS-59403 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

This is an automated cherry-pick of #9481

/assign haircommander

None

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has DCO signed all their commits. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. release-note-none Denotes a PR that doesn't merit a release note.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants