[release-4.14][manual] OCPBUGS-30980: irqbalance: set banned cpus list to '0'

[yanirq]

Manual cherry-pick of #953

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yanirq

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yanirq]

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

[openshift-cherrypick-robot]

@yanirq: once the present PR merges, I will cherry-pick it on top of OCPBUGS-27227 in a new PR and assign it to you.

In response to this:

/cherry-pick OCPBUGS-27227

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/test-infra repository.

[yanirq]

/jira cherrypick OCPBUGS-27227

[openshift-ci-robot]

@yanirq: Jira Issue OCPBUGS-27227 has been cloned as Jira Issue OCPBUGS-30980. Will retitle bug to link to clone.
/retitle OCPBUGS-30980: irqbalance: set banned cpus list to '0'

In response to this:

/jira cherrypick OCPBUGS-27227

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]

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

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-27227 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-27227 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @gsr-shanks

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

In response to this:

Manual cherry-pick of #953

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.

[yanirq]

/uncc @gsr-shanks
/cc @SargunNarula @mrniranjan

[openshift-ci]

@yanirq: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

[yanirq]

/label backport-risk-assessed

[Tal-or]

/lgtm

[mrniranjan]

/label cherry-pick-approved

[openshift-ci-robot]

@yanirq: Jira Issue OCPBUGS-30980: All pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#994

Jira Issue OCPBUGS-30980 has been moved to the MODIFIED state.

In response to this:

Manual cherry-pick of #953

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-node-tuning-operator-container-v4.14.0-202403191142.p0.gd8d9739.assembly.stream.el9 for distgit cluster-node-tuning-operator.
All builds following this will include this PR.

[yanirq]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@yanirq: #994 failed to apply on top of branch "release-4.13":

Applying: irqbalance: set banned cpus list to 0
Using index info to reconstruct a base tree...
M	test/e2e/performanceprofile/functests/1_performance/irqbalance.go
A	test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
A	test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
CONFLICT (modify/delete): test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml deleted in HEAD and modified in irqbalance: set banned cpus list to 0. Version irqbalance: set banned cpus list to 0 of test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml left in tree.
Auto-merging test/e2e/performanceprofile/functests/1_performance/irqbalance.go
CONFLICT (content): Merge conflict in test/e2e/performanceprofile/functests/1_performance/irqbalance.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 irqbalance: set banned cpus list to 0
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.13

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/test-infra repository.