Skip to main content
NetApp Knowledge Base

Requesting a persistent volume in Trident returns with an EOF error

Last Updated:

Applies to

  • Trident for Kubernetes 19.07 and higher
  • Trident for Openshift 19.07 and higher


The following error ends the PV creation attempt: Post "": EOF

Additional symptoms and behavior seen:

  • worker nodes have full connectivity and resolve all names correctly
  • /etc/resolv.conf in worker nodes have a "search domains" directive, that works as expected
  • pods running on these worker nodes will inherit options and search domains from their host, and add a ndots:5 directive
  • pods only resolve FQDNs, but when removing "ndots:5" or search domains inside the pod, the pod is able to resolve any name
  • apart from name resolution, some destinations are unreachable (ping : no route to host)
  • the kube-apiserver is slow to answer any query with kubectl
  • an ONTAPI https request test to the SVM shows that it's responding normally to, for example a system-get-version API call (*)


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.