Skip to main content
NetApp Knowledge Base

Pod restart fails after worker node loses access to NFS PV

  1. Last updated
    Mar 5, 2025
  2. Save as PDF
Views:
112
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:
3/5/2025, 2:10:23 PM

Applies to

  • NetApp Astra Trident
  • NFS Persistent Volume (PV)

Issue

  • Pod restart fails after worker node loses access to NFS PV
  • Manually mounting the NFS PV on the worker node fails
  • kubectl describe pod <POD> reports warnings:

  Warning  FailedMount  40s                  kubelet                  MountVolume.SetUp failed for volume "<PVC>" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
  Warning  FailedMount  28s (x2 over 2m32s)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[<VOLUME>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

 

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.