Skip to main content
NetApp Knowledge Base

Trident BackendConfig Fails to Reconcile After Upgrade Due to Duplicate Backend Name

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

Applies to

  • NetApp Trident 26.02
  • Kubernetes clusters using Trident CSI
  • OpenShift Container Platform (OCP)
  • KubeVirt
  • Trident Backend Config (TBC)
  • Environments managed by ArgoCD

Issue

After upgrading Trident, VM provisioning and Persistent Volume operations failed. The TridentBackendConfig resource was stuck in a failed state with repeated log messages:

Failed to apply the backend update; Trident initialization failed; key <backend name> for Backend already exists

Trident controller logs showed repeated reconciliation failures:

Warning Failed trident-crd-controller Failed to apply the backend update; Trident initialization failed; key <backend name> for Backend already exists

Persistent Volumes were referencing only one backend UUID, but two backend objects existed in Trident with the same backend name.

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.