1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/cluster-node-tuning-operator-verify-profiles.adoc
Max Bridges b5fc467d1f add content types to untagged modules
OSDOCS-16694
2025-10-31 21:02:28 -04:00

50 lines
2.1 KiB
Plaintext

// Module included in the following assemblies:
//
// * scalability_and_performance/using-node-tuning-operator.adoc
:_mod-docs-content-type: PROCEDURE
[id="verifying-tuned-profiles-are-applied_{context}"]
= Verifying that the TuneD profiles are applied
Verify the TuneD profiles that are applied to your cluster node.
[source,terminal]
----
$ oc get profile.tuned.openshift.io -n openshift-cluster-node-tuning-operator
----
.Example output
[source,terminal]
----
NAME TUNED APPLIED DEGRADED AGE
master-0 openshift-control-plane True False 6h33m
master-1 openshift-control-plane True False 6h33m
master-2 openshift-control-plane True False 6h33m
worker-a openshift-node True False 6h28m
worker-b openshift-node True False 6h28m
----
* `NAME`: Name of the Profile object. There is one Profile object per node and their names match.
* `TUNED`: Name of the desired TuneD profile to apply.
* `APPLIED`: `True` if the TuneD daemon applied the desired profile. (`True/False/Unknown`).
* `DEGRADED`: `True` if any errors were reported during application of the TuneD profile (`True/False/Unknown`).
* `AGE`: Time elapsed since the creation of Profile object.
The `ClusterOperator/node-tuning` object also contains useful information about the Operator and its node agents' health. For example, Operator misconfiguration is reported by `ClusterOperator/node-tuning` status messages.
To get status information about the `ClusterOperator/node-tuning` object, run the following command:
[source,terminal]
----
$ oc get co/node-tuning -n openshift-cluster-node-tuning-operator
----
.Example output
[source,terminal,subs="attributes+"]
----
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
node-tuning {product-version}.1 True False True 60m 1/5 Profiles with bootcmdline conflict
----
If either the `ClusterOperator/node-tuning` or a profile object's status is `DEGRADED`, additional information is provided in the Operator or operand logs.