Skip to main content
NetApp Knowledge Base

Trident backend not available when doing a switchover in a MetroCluster, when using REST APIs

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

Applies to

  • Trident
  • Trident Backend (TBE)
  • Metrocluster (MCC) switchover
  • REST APIs

Issue

  • After an MCC switchover, the TBE is showing as Invalid backend state with the error seen in the Trident logs:

level=error msg="Invalid backend state." expectedState=online/deleting logLayer=core requestID=89998fab-7f04-4744-970c-1d419f0c4c28 requestSource=CSI state=failed workflow="controller=publish"
level=error msg="Invalid backend state." expectedState=online/deleting state=offline workflow="core=node_reconcile" (112K+ occurrences)
level=error msg="backend <backend_name> is not Online or Deleting"
REST API calls to https:/<IP_Address>/api/storage/qtrees returning context deadline exceeded

  • This applies to all backend drivers using REST API calls

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.