[release-4.20] OCPBUGS-66364: Add support for lscpu_check TuneD built-in by openshift-cherrypick-robot · Pull Request #1443 · openshift/cluster-node-tuning-operator

openshift-cherrypick-robot · 2025-12-03T21:08:45Z

This is an automated cherry-pick of #1439

/assign jmencak

This change adds support for lscpu_check TuneD built-in. Other changes * Drop the severity from ERROR to WARNING in execTuneDBuiltin() * Be more specific what is the impact of calling unsupported TuneD built-in function Resolves: OCPBUGS-66214

openshift-ci-robot · 2025-12-03T21:08:56Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-66214 has been cloned as Jira Issue OCPBUGS-66364. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-66364: Add support for lscpu_check TuneD built-in

Details

In response to this:

This is an automated cherry-pick of #1439

/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 · 2025-12-03T21:09:12Z

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

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-66214 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

Details

In response to this:

This is an automated cherry-pick of #1439

/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 · 2025-12-04T06:09:44Z

/approve
/lgtm
/label backport-risk-assessed
/jira refresh

openshift-ci-robot · 2025-12-04T06:09:48Z

@jmencak: This pull request references Jira Issue OCPBUGS-66364, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

In response to this:

/approve
/lgtm
/label backport-risk-assessed
/jira refresh

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 · 2025-12-04T06:10:10Z

[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:

~~OWNERS~~ [jmencak]

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

jmencak · 2025-12-04T06:11:02Z

/jira refresh

openshift-ci-robot · 2025-12-04T06:11:07Z

@jmencak: This pull request references Jira Issue OCPBUGS-66364, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

Details

In response to this:

/jira refresh

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 · 2025-12-04T06:12:08Z

/jira refresh

openshift-ci-robot · 2025-12-04T06:12:16Z

@jmencak: This pull request references Jira Issue OCPBUGS-66364, 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.20.z) matches configured target version for branch (4.20.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-66214 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-66214 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (liqcui@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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 · 2026-03-04T09:00:37Z

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot · 2026-04-04T00:30:53Z

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

coderabbitai · 2026-04-04T00:31:03Z

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c9be3736-1b56-4325-9ffd-956f4db0ae75

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

jmencak · 2026-04-10T09:11:35Z

/verified later @shyadav10

openshift-ci-robot · 2026-04-10T09:11:48Z

@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-merge-bot · 2026-04-10T12:24:37Z

/retest-required

Remaining retests: 0 against base HEAD b1f1c24 and 2 for PR HEAD e095624 in total

openshift-ci · 2026-04-10T13:15:10Z

@openshift-cherrypick-robot: The following tests 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-hypershift-pao	`e095624`	link	unknown	`/test e2e-hypershift-pao`
ci/prow/e2e-hypershift	`e095624`	link	true	`/test e2e-hypershift`

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.

Add support for lscpu_check TuneD built-in

e095624

This change adds support for lscpu_check TuneD built-in. Other changes * Drop the severity from ERROR to WARNING in execTuneDBuiltin() * Be more specific what is the impact of calling unsupported TuneD built-in function Resolves: OCPBUGS-66214

openshift-cherrypick-robot assigned jmencak Dec 3, 2025

openshift-cherrypick-robot mentioned this pull request Dec 3, 2025

OCPBUGS-66214: Add support for lscpu_check TuneD built-in #1439

Merged

openshift-ci bot changed the title ~~[release-4.20] OCPBUGS-66214: Add support for lscpu_check TuneD built-in~~ [release-4.20] OCPBUGS-66364: Add support for lscpu_check TuneD built-in Dec 3, 2025

openshift-ci bot requested review from jmencak and swatisehgal December 3, 2025 21:09

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 4, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 4, 2025

openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2026

openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 4, 2026

openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Apr 10, 2026

Conversation

openshift-cherrypick-robot commented Dec 3, 2025

Uh oh!

openshift-ci-robot commented Dec 3, 2025

Uh oh!

openshift-ci-robot commented Dec 3, 2025

Uh oh!

jmencak commented Dec 4, 2025

Uh oh!

openshift-ci-robot commented Dec 4, 2025

Uh oh!

openshift-ci bot commented Dec 4, 2025

Uh oh!

jmencak commented Dec 4, 2025

Uh oh!

openshift-ci-robot commented Dec 4, 2025

Uh oh!

jmencak commented Dec 4, 2025

Uh oh!

openshift-ci-robot commented Dec 4, 2025

Uh oh!

openshift-bot commented Mar 4, 2026

Uh oh!

openshift-bot commented Apr 4, 2026

Uh oh!

coderabbitai bot commented Apr 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

jmencak commented Apr 10, 2026

Uh oh!

openshift-ci-robot commented Apr 10, 2026

Uh oh!

openshift-merge-bot bot commented Apr 10, 2026

Uh oh!

openshift-ci bot commented Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

coderabbitai bot commented Apr 4, 2026 •

edited

Loading