Skip to main content
NetApp Stage KB

Trident fails to provision volumes in a timely fashion, leaving pods waiting

Applies to

Astra Trident for Kubernetes and Openshift


When adding an application with pods to the Kubernetes or Openshift cluster, using Trident PVs, the PVs, PVCs and PODs are delayed for a long time before coming up.
Messages seen are:

Unable to attach or mount volumes: unmounted volumes=[PV_NAME], unattached volumes=[PV_NAME_2 PV_NAME PV_NAME_3 ...]: timed out waiting for the condition
AttachVolume.Attach failed for volume "pvc-UUID" : rpc error: code = DeadlineExceeded desc = context deadline exceeded


Additional errors from Trident give more context:

  • Trident logs show errors on volume creation and deletion:

backend cannot satisfy create request for volume trident_<PREFIX>_pvc_<UUID>: (ONTAP-NAS pool <AGGR>/<AGGR>; error creating volume trident_<PREFIX>_pvc_<UUID>: API status: failed,Reason: Failed to create the volume on node \"<STORAGE_NODE>\".Reason: Failed to store NVE key with key ID\"00000000000000000200000000000HEX-UUID0000000000000000\" on external key server \"<HOST_FQDN>:50100\

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.