TridentBackendConfig : failed to create backend, update initiated using an invalid configRef

Describe the bug I am receiving this error every time I delete and regenerate trident opearot

status:
  backendInfo:
    backendName: ''
    backendUUID: ''
  deletionPolicy: delete
  lastOperationStatus: Failed
  message: >-
    Failed to create backend: backend 'Backend-XX-XX-X-XX-XX' update
    initiated using an invalid configRef, it is associated with configRef
    '1548424b-a9ff-4708-bc4c-d3e87cc381dc' and not
    '6f8e9eaa-dc62-4221-b57d-67008f2c7828'
  phase: ''

Environment Provide accurate information about the environment to help us reproduce the issue.

Trident version: 24.06.1
Trident installation flags used: [From ArgoCD]
Container runtime: [e.g. Docker 25.x.x-CE]
Kubernetes version: [e.g. 1.15.1]
Kubernetes orchestrator: [Rancher v2.9.1]
OS: [Oracle Linux 8.9]
NetApp backend types: Ontap
Other:

To Reproduce Install trident operator with the following TridentBackedConfig

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
  creationTimestamp: '2024-11-12T10:29:01Z'
  finalizers:
    - trident.netapp.io
  generation: 1
  labels:
    app: operator.trident.netapp.io
    argocd.argoproj.io/instance: trident-operator
  name: backend-config-ontap-nas
  namespace: trident-operator
  resourceVersion: '509161649'
  uid: 6f8e9eaa-dc62-4221-b57d-67008f2c7828
spec:
  backendName: Backend-XX-XX-X-XX-XX
  credentials:
    name: ontap-nas-secret
  debugTraceFlags:
    api: false
    method: false
  defaults:
    snapshotPolicy: none
    spaceReserve: none
  igroupName: ig_nfs_xx_xx_xx
  labels:
    backend: nas_store
  limitVolumeSize: 150G
  managementLIF: svm_xx_x_xx_x_x.yoksetio.com
  storage:
    - labels:
        dc: xx_xx
  storageDriverName: ontap-nas
  storagePrefix: xx_xx_xx_xx_xx
  svm: xx_xx_xx_xx_xx
  version: 1
status:
  backendInfo:
    backendName: ''
    backendUUID: ''
  deletionPolicy: delete
  lastOperationStatus: Failed
  message: >-
    Failed to create backend: backend 'Backend-XX-XX-X-XX-XX' update
    initiated using an invalid configRef, it is associated with configRef
    '1548424b-a9ff-4708-bc4c-d3e87cc381dc' and not
    '6f8e9eaa-dc62-4221-b57d-67008f2c7828'
  phase: ''

Expected behavior

apiVersion: trident.netapp.io/v1
kind: TridentBackendConfig
metadata:
  creationTimestamp: '2024-11-12T10:29:01Z'
  finalizers:
    - trident.netapp.io
  generation: 1
  labels:
    app: operator.trident.netapp.io
    argocd.argoproj.io/instance: trident-operator
  name: backend-config-ontap-nas
  namespace: trident-operator
  resourceVersion: '509161649'
  uid: 1548424b-a9ff-4708-bc4c-d3e87cc381dc
spec:
  backendName: Backend-XX-XX-X-XX-XX
  credentials:
    name: ontap-nas-secret
  debugTraceFlags:
    api: false
    method: false
  defaults:
    snapshotPolicy: none
    spaceReserve: none
  igroupName: ig_nfs_xx_xx_xx
  labels:
    backend: nas_store
  limitVolumeSize: 150G
  managementLIF: svm_xx_x_xx_x_x.yoksetio.com
  storage:
    - labels:
        dc: xx_xx
  storageDriverName: ontap-nas
  storagePrefix: xx_xx_xx_xx_xx
  svm: xx_xx_xx_xx_xx
  version: 1

Additional context N/A.

NetApp / trident

TridentBackendConfig : failed to create backend, update initiated using an invalid configRef #948