Using Trident to create a TBC for existing backend fails with configRef error
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.