Cluster node tuning operator pod in Preempting state

Solution Verified - Updated -

Issue

  • Cluster node tuning operator pod in Preempting state.
# oc get pods -n openshift-cluster-node-tuning-operator -o wide
NAME                              READY      STATUS       RESTARTS   AGE       IP             NODE              NOMINATED NODE   READINESS GATES
cluster-node-tuning-operator-xxx   1/1       Running      0          130m      10.254.4.93    master0.example.com   <none>           <none>
cluster-node-tuning-operator-yyy   0/1       Preempting   0          4d2h      <none>         master1.example.com   <none>           <none>
  • Master had the profile assigned but not to the worker nodes
# for i in `oc get pods -n openshift-cluster-node-tuning-operator | cut -d " " -f1 | grep tuned`; do echo "" && echo "*** $i ***" && oc logs pod/$i -n openshift-cluster-node-tuning-operator | grep applied; done

*** tuned-24tqz ***
2020-05-12 17:13:53,099 INFO     tuned.daemon.daemon: static tuning from profile 'openshift-control-plane' applied

*** tuned-2scsm ***

*** tuned-fczss ***
2020-05-12 17:14:08,191 INFO     tuned.daemon.daemon: static tuning from profile 'openshift-control-plane' applied

*** tuned-k997f ***

*** tuned-r5mgn ***

*** tuned-sqq6q ***
2020-05-12 17:14:12,089 INFO     tuned.daemon.daemon: static tuning from profile 'openshift-control-plane' applied

Environment

  • OpenShift Container Platform
    • 4.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content