Skip to main content
NetApp Knowledge Base

Trident OpenShift reports stale NFile handle

Views:
428
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Trident OpenShift

Issue

OpenShift system appears not able to connect to NetApp storage with following error message:

Jun 03 00:00:42 localhost_machine.com atomic-openshift-node[38440]: E0603 00:00:42.794548   38440 nestedpendingoperations.go:262] Operation for "\"kubernetes.ifs/1234567-1234-12e3-8ce1-1234567c3f40-abc-cl1-t1p0-ldap-net-fc843\" (\"1234567-1234-12e3-8ce1-1234567c3f40\")" failed. No retries permitted until 2018-06-03 00:42.794500202 -0400 EDT (durationBeforeRetry 2m0s). Error: UnmountVolume.TearDown failed for volume "kubernetes.io/nfs/1234567-1234-12e3-8ce1-1234567c3f40-abc-cl1p0-ldap-net-fc843" (volume.spec.Name: "net-data") pod "1234567-1234-12e3-8ce1-1234567c3f40" (UID: "1234567-1234-12e3-8ce1-1234567c3f40") with: Error checking iath exists: stat /var/lib/origin/openshift.local.volumes/pods/1234567-1234-12e3-8ce1-1234567c3f40/volumes/kubernetes.io~nfs/abc-cl1-t1p0-ldap-net-fc  843: stale NFile handle

 

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.