Skip to main content
NetApp Knowledge Base

Creating pod fails when worker node lacks IP for NFS communication

  1. Last updated
  2. Save as PDF
Views:
148
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Astra Trident
  • Worker node having no IP address for NFS communication
  • Pod that is assigned dynamic IP address  for NFS communication after it is created
  • NFS Persistent Volume (PV)

Issue

  • Creating pod using NFS PV created by Trident fails
  • kubectl describe pod <POD> reports warnings:

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

  Warning  FailedMount             38s    kubelet                  Unable to attach or mount volumes: unmounted volumes=[<VOLUME>], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
  Warning  FailedMount             32s    kubelet                  MountVolume.SetUp failed for volume "<PVC>" : rpc error: code = Internal desc = error mounting NFS volume <IP>:/<NFS> on mountpoint /var/lib/kubelet/pods/<ID>/volumes/kubernetes.io~csi/<PVC>/mount: exit status 32

  • Creating pod without mounting PV succeeds, and NFS mounts using mount command in the pod succeeds.

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.