Skip to main content
NetApp Knowledge Base

Trident mount volume failed with the error "context deadline exceeded"

  1. Last updated
  2. Save as PDF
Views:
1,465
Visibility:
Public
Votes:
10
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Astra Trident

Issue

  • Unable to mount the volumes in application pods for some or all worker nodes in the Kubernetes cluster
  • Manual mount is successful when performed directly from the worker node.
  • Mounting the volume in an application pod fails with the error below:

# kubectl describe pod <application-pod-name> -n <pod-namespace>

Warning  FailedMount  16m (x382 over 18h)    kubelet  Unable to attach or mount volumes: unmounted volumes=[xxxxx], unattached volumes=[xxxxx xxxxx]: timed out waiting for the condition
Warning  FailedMount  9m45s (x117 over 18h)  kubelet  Unable to attach or mount volumes: unmounted volumes=[xxxxx], unattached volumes=[xxxxxx xxxxx]: timed out waiting for the condition
Warning  FailedMount  81s (x286 over 18h)    kubelet  MountVolume.MountDevice failed for volume "pvc-xxxxx" : 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.