Skip to main content
NetApp Knowledge Base

Pods Unable to Spin Up Due to “Failed Attach Volume” Error in OpenShift with NetApp Trident

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

Applies to

  • OpenShift clusters using NetApp Trident CSI
  • Environments with ElasticSearch pods and ONTAP SAN backends

Issue

ElasticSearch pods fail to spin up and display the following error in their description:

Warning FailedAttachVolume 4m12s (x6719 over 139m) attachdetach-controller AttachVolume.Attach failed for volume "pvc-xxx": rpc error: code=Unknown desc=backend <backend name> is not Online or Deleting

Additionally, network connectivity tests from the node hosting the Trident controller pod to the storage management LIF (Logical Interface) fail with errors:

  • “No route to host”
  • “Destination Host Unreachable”

The Trident backend is reported as “not Online or Deleting” and volume attachments cannot be established.

 

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.