Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

jmencak
Copy link
Contributor

@jmencak jmencak commented Apr 3, 2025

NTO Tuned CRs support machine config labels (mcLabels) based matching. This involves finding a MachineConfigPool with machineConfigSelector matching mcLabels and setting a TuneD profile on all nodes that are assigned the found MachineConfigPool. We do not support configurations, where more than 1 MachineConfigPool matches the mcLabels. While this configuration is not supported, users often unwittingly configure their clusters in this way. In this case, NTO issues an error message in the operator logs.

This is often not sufficient, so we make this misconfiguration more visible by making ClusterOperator/node-tuning object Degraded.

NTO Tuned CRs support machine config labels (mcLabels) based matching.
This involves finding a MachineConfigPool with machineConfigSelector
matching mcLabels and setting a TuneD profile on all nodes that are
assigned the found MachineConfigPool.  We do not support configurations,
where more than 1 MachineConfigPool matches the mcLabels.  While this
configuration is not supported, users often unwittingly configure
their clusters in this way.  In this case, NTO issues an error message
in the operator logs.

This is often not sufficient, so we make this misconfiguration more
visible by making ClusterOperator/node-tuning object Degraded.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 3, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 3, 2025

@jmencak: This pull request references PSAP-1655 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

NTO Tuned CRs support machine config labels (mcLabels) based matching. This involves finding a MachineConfigPool with machineConfigSelector matching mcLabels and setting a TuneD profile on all nodes that are assigned the found MachineConfigPool. We do not support configurations, where more than 1 MachineConfigPool matches the mcLabels. While this configuration is not supported, users often unwittingly configure their clusters in this way. In this case, NTO issues an error message in the operator logs.

This is often not sufficient, so we make this misconfiguration more visible by making ClusterOperator/node-tuning object Degraded.

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 requested review from MarSik and swatisehgal April 3, 2025 06:47
Copy link
Contributor

openshift-ci bot commented Apr 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 3, 2025
@jmencak
Copy link
Contributor Author

jmencak commented May 12, 2025

/retest

Copy link
Contributor

openshift-ci bot commented May 12, 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-bot
Copy link
Contributor

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-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 11, 2025
@jmencak
Copy link
Contributor Author

jmencak commented Aug 11, 2025

/remove-lifecycle stale
I still believe there is value in this PR. Any reviews? Thanks.

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 11, 2025
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants