Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-16324

[tracker] kubelet fails to start: wrong number of fields (BZ#2236529)

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      kubelet cannot start (wrong number of fields) if fstab contains a space character for source
      
      /proc/mounts contains the extra space character making the List call to see 7 fields instead of 6.

      Version-Release number of selected component (if applicable):

      OpenShift 4.10 > 4.11 upgrade
      

      How reproducible:

      All the time in nodes that mounts a filesystem through fstab definition with a space in source
      

      Steps to Reproduce:

      1. Define a source location with a space in fstab in the node 
      2. Upgrade OCP (a restart of kubelet might also trigger this issue) 

      Actual results:

      kubelet won't start with a message similar to:
      
      "Failed to start ContainerManager" err="system validation failed - wrong number of fields (expected 6, got 7)"
      
      MachineConfigPool won't progress with upgrades on nodes.
      

      Expected results:

      kubelet service able to start and upgrade process to complete
      

      Additional info:

      Seems to be a regression since this behavior wasn't seen in 4.10 version.
      
      Workaround: umount the fileshare from the node while upgrade happens, mount it afterwards.

              mnguyen@redhat.com Michael Nguyen
              rhn-support-jcoscia Javier Coscia
              Sunil Choudhary Sunil Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: