Restorecon failure in OCP 4.18, causing kubelet to not start

Solution Verified - Updated -

Issue

  • When upgrading from 4.17 to 4.18 the node gets stuck into Not Ready and the upgrade does not succeed.
  • Node is stuck in NotReady state with below error :
Mar 25 17:09:09 nodename restorecon[4121]: /var/lib/kubelet/pods/xxx/etc-hosts not reset as customized by admin to system_u:object_r:container_file_t:s0:c24,c27

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.18.0 to 4.18.12

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