High CPU utilization and timeouts leading to system crashes in RHOCP

Solution Verified - Updated -

Issue

  • Observed high cpu utilization in node and failing mounting with Connection timed out

      Type     Reason       Age                    From     Message
      ----     ------       ----                   ----     -------
      Warning  FailedMount  163m (x93 over 6h14m)  kubelet  MountVolume.SetUp failed for volume "siptls-ca" : mount failed: exit status 1
      Mounting command: systemd-run
      Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/0b94f3d8-4449-451a-9147-e0e64230ee1f/volumes/kubernetes.io~secret/siptls-ca --scope -- mount -t tmpfs tmpfs /var/lib/kubelet/pods/0b94f3d8-4449-451a-9147-e0e64230ee1f/volumes/kubernetes.io~secret/siptls-ca
      Output: Failed to start transient scope unit: Connection timed out
        Warning  FailedMount  134m (x105 over 6h14m)  kubelet  MountVolume.SetUp failed for volume "client-ca" : mount failed: exit status 1
      Mounting command: systemd-run
    
  • Pod stuck in ContainerCreating with error Connection timed out

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.6
    • 4.7
    • 4.8
  • Red Hat Enterprise Linux (RHEL)
    • 8

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