Skip to main content
NetApp Knowledge Base

Pod is unable to mount PVC when IPsec tunnel is established

Views:
15
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP 9.X
  • AFF
  • Kubernetes
  • NFS

Issue

  • When trying to create a pod in Kubernetes with a Persistent Volume Claim (PVC) while IPsec is enabled, the pod fails to mount the PVC.
  • The following errors observed in the Worker Nodes:
    Events:
      Type     Reason                  Age                From                     Message
      ----     ------                  ----               ----                     -------
      Warning  FailedScheduling        30m (x3 over 30m)  default-scheduler        0/4 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.
      Normal   Scheduled               30m                default-scheduler        Successfully assigned (Kubernetes Cluster) to (Pool Name)
      Normal   SuccessfulAttachVolume  30m                attachdetach-controller  AttachVolume.Attach succeeded for volume "(Volume Name)"
      Warning  FailedMount             15m (x3 over 27m)  kubelet                  MountVolume.SetUp failed for volume "(Volume Name)" : rpc error: code = Aborted desc = request waited too long for the lock
      Warning  FailedMount             9s  (x9 over 28m)  kubelet                  MountVolume.SetUp failed for volume "(Volume Name)" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
 

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.