OCP Node cannot rejoin cluster after reboot due to ocp-tuned-one-shot.service failure

Solution Verified - Updated -

Issue

  • After a reboot, a OCP node becomes NotReady and fails to rejoin the cluster:

    $ oc get node
NAME    STATUS                       ROLES                         AGE    VERSION
master0 NotReady,SchedulingDisabled  control-plane,master,worker   195d   v1.27.16+03a907c
master1 Ready                        control-plane,master,worker   195d   v1.27.16+03a907c
master2 Ready                        control-plane,master,worker   195d   v1.27.16+03a907c
worker0 Ready                        worker                        195d   v1.27.16+03a907c
worker1 Ready                        worker                        195d   v1.27.16+03a907c
worker2 Ready                        worker                        195d   v1.27.16+03a907c

  • On the node, ocp-tuned-one-shot.service is marked as failed

    # systemctl status ocp-tuned-one-shot.service

× ocp-tuned-one-shot.service - TuneD service from NTO image
     Loaded: loaded (/etc/systemd/system/ocp-tuned-one-shot.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2025-01-01 00:00:00 UTC; 4min 17s ago
         :

Environment

  • Red Hat Openshift Container Platform 4.14.38 or lower
  • Red Hat Openshift Container Platform 4.15.35 or lower
  • Red Hat Openshift Container Platform 4.16.14 or lower
  • Red Hat Openshift Container Platform 4.17.0
  • Red Hat Openshift Container Platform 4.18.0
  • Cluster-wide proxy configured

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