Skip to main content
NetApp Knowledge Base

Using Trident to create a TBC for existing backend fails with configRef error

Views:
605
Visibility:
Public
Votes:
2
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Trident for Openshift or Kubernetes

Issue

When using a version of trident that supports the creation of the Kubernetes TBC for a pre-existing Trident backend, attempting to do so creates the TBC, but fails to link it  to the backend. Running kubectl describe tbc <TBC_NAME> shows the error:
Failed to create backend: backend '<TBE_NAME>' update initiated using an invalid configRef,
it is associated with configRef '<OLD_TBC_UID>' and not '<NEW_TBC_UID>'
 
This only happens when:
  • a TBC has existed before (*), or
  • still exists for that Trident backend, in which case you don't need to create another TBC in the first place.

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.