Skip to main content
NetApp Knowledge Base

Trident Volumes “Deadline Exceeded” Error During VM Migration in OpenShift

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident (ONTAP-SAN driver, version 26.02.1 and earlier)
  • OpenShift/Kubernetes clusters using Trident for persistent volumes
  • NetApp AFF-A250 running ONTAP 9.17.1P6
  • Environments with high concurrent snapshot/clone operations (e.g., Commvault backups)

Issue

During VM migrations in an OpenShift cluster using NetApp Trident, VMs become stuck with “deadline exceeded” errors, resulting in failed or delayed volume attaches. This is often observed during periods of heavy backup or snapshot activity.

Example log output:

rpc error: code = DeadlineExceeded desc = context deadline exceeded
Warning  FailedMapVolume  kubelet  MapVolume.SetUpDevice failed for volume "<pvc_name>": rpc error: code = DeadlineExceeded desc = context deadline exceeded
MountVolume.MountDevice failed for volume "<pvc_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.