Skip to main content
NetApp Knowledge Base

Pods stuck in ContainerCreating due to NFS timeouts

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • IPv6
  • Red Hat OpenShift (Kubernetes) (optional)
  • Trident 25.02.1 (optional)

Issue

  • Multiple Kubernetes pods remain stuck in 'ContainerCreating' state due to repeated NFS timeout errors.
  • Error messages observed on worker nodes include:
    • Warning FailedMount kubelet Unable to attach or mount volumes: timed out waiting for the condition
    • nfs: server 26a0:f160:ff09:f021:b1:fe0:0:3139 not responding, timed out
  • The impacted NFS data LIF became unresponsive.
  • LIF migration temporarily restores data access.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.