Skip to main content
NetApp Knowledge Base

OpenShift Pods Fail to Start After SVM DR Failover/Failback with NetApp Trident — “backend BackendForNFS is not Online or Deleting”

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

Applies to

  • NetApp ONTAP SVM Disaster Recovery (SVM DR) environments
  • NetApp Trident CSI Driver
  • Kubernetes/OpenShift clusters using Trident for ONTAP storage
  • SnapMirror SVM DR relationships (Identity Preserve = true)
  • ONTAP 9.x (example: 9.15.1P10)
  • Trident-managed NFS volumes

Issue

After performing a DR test by failing over to the DR SVM and then failing back to the primary SVM, OpenShift pods fail to come online. The following error is seen in the pod events and Trident logs:

AttachVolume.Attach failed for volume "pvc-uuid" : rpc error: code = Unknown desc = backend <backend name> is not Online or Deleting

Pods remain in a “ContainerCreating” or “Pending” state, and Persistent Volume Claims (PVCs) are not attached.

 

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.