kubelet fails to start: system validation failed - wrong number of fields

Solution In Progress - Updated -

Issue

  • While upgrading the OpenShift cluster from version 4.10 to 4.11, the worker MachineConfigPool stays in progressing and node remains in NotReady
  • Kubelet service on NotReady node cannot start due to a 'wrong number of fields' if fstab contains a space character for source location
  • /proc/mounts contains the extra space character making the List call to see 7 fields instead of 6.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
  • Upgrade from 4.10 to 4.11

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