Skip to main content
NetApp Stage KB

POD with Trident SAN or NAS RWO PV goes offline when moving to another node

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

  • Openshift/Kubernetes
  • SAN/iSCSI PVs
  • NAS RWO PVs
  • Trident

Issue

The following error occurs in a replacement pod, when the original pod using the PV fails or is deleted on its node and Kuberenetes is attempting to start it up on one of the other nodes, while the pod is using an RWO based PVC, such as those using an iSCSI ontap-san backend, but also NFS RWO type PV:

Multi-Attach error for volume "pvc-<UUID>" Volume is already exclusively attached to one node and can't be attached to another

However, after a while the only error left is:

Warning FailedMount <time_delay> kubelet MountVolume.MountDevice failed for volume  "pvc-<UUID>" : 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.
67856310-fe58-4b67-8866-1d497fbcdf0d