Skip to content

Conversation

@jmencak
Copy link
Contributor

@jmencak jmencak commented Dec 2, 2025

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

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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

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

In response to this:

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

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 2, 2025
@openshift-ci openshift-ci bot requested review from Tal-or and ffromani December 2, 2025 13:08
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 2, 2025
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
@jmencak jmencak force-pushed the 4.21-OCPBUGS-66214 branch from c3ca499 to 01b40b7 Compare December 2, 2025 13:12
@jmencak jmencak changed the title WiP: OCPBUGS-66214: Add support for lscpu_check TuneD built-in OCPBUGS-66214: Add support for lscpu_check TuneD built-in Dec 2, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 2, 2025
@jmencak
Copy link
Contributor Author

jmencak commented Dec 2, 2025

I've manually verified this error no longer appears when using this CR on SNO:

apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: openshift-profile
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
  - data: |
      [main]
      summary=Custom OpenShift profile
      include=openshift-node${f:lscpu_check:.:}
    name: openshift-profile
  recommend:
  - machineConfigLabels:
      machineconfiguration.openshift.io/role: "master"
    priority: 18
    profile: openshift-profile

@MarSik
Copy link
Contributor

MarSik commented Dec 3, 2025

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, MarSik

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:

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

Copy link
Contributor

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@jmencak
Copy link
Contributor Author

jmencak commented Dec 3, 2025

@liqcui , would you be able to provide pre-merge verification for this? It should be pretty easy, just create the manifest above on a regular cluster. Thank you!

@liqcui
Copy link

liqcui commented Dec 3, 2025

/verified by @liqcui

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 3, 2025
@openshift-ci-robot
Copy link
Contributor

@liqcui: This PR has been marked as verified by @liqcui.

In response to this:

/verified by @liqcui

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
Copy link
Contributor Author

jmencak commented Dec 3, 2025

This should go to 4.21.0
/label acknowledge-critical-fixes-only

@jmencak
Copy link
Contributor Author

jmencak commented Dec 3, 2025

/retest

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

@jmencak: 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 629b12f into openshift:main Dec 3, 2025
18 checks passed
@openshift-ci-robot
Copy link
Contributor

@jmencak: Jira Issue Verification Checks: Jira Issue OCPBUGS-66214
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-66214 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

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

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 deleted the 4.21-OCPBUGS-66214 branch December 3, 2025 21:07
@jmencak
Copy link
Contributor Author

jmencak commented Dec 3, 2025

/cherry-pick release-4.20

@openshift-cherrypick-robot

@jmencak: new pull request created: #1443

In response to this:

/cherry-pick release-4.20

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

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants