#TridentBackendConfig in deletion state, how can I stop it?

1 messages · Page 1 of 1 (latest)

inland hazel
#

I have, accidentally, deleted the tbc that had a deletionPolicy set to delete, and now my backend with many volumes is in deletion state. How can I stop the deletion process of the backend?

15:35 # tridentctl get backends -n trident
+----------------------+----------------+--------------------------------------+----------+---------+
|         NAME         | STORAGE DRIVER |                 UUID                 |  STATE   | VOLUMES |
+----------------------+----------------+--------------------------------------+----------+---------+
| ontapsan_10.11.6.112 | ontap-san      | 69deda8f-f15b-46e1-8ee8-bbd23f6617d9 | deleting |      33 |
| ontapnas_10.11.5.186 | ontap-nas      | 4a2130d2-a2a0-4f9d-9928-9ecae99d5693 | online   |     169 |
inland hazel
# 
16:05 # kubectl get tbc -n trident 
NAME                     BACKEND NAME           BACKEND UUID                           PHASE   STATUS
backend-ontap-nas-main   ontapnas_10.11.5.186   4a2130d2-a2a0-4f9d-9928-9ecae99d5693   Bound   Success

At some point it was not listed here (before it was in deletion state)

the tridentclt was still having it as deleting:

16:04 # tridentctl get backends -n trident
+----------------------+----------------+--------------------------------------+----------+---------+
|         NAME         | STORAGE DRIVER |                 UUID                 |  STATE   | VOLUMES |
+----------------------+----------------+--------------------------------------+----------+---------+
| ontapsan_10.11.6.112 | ontap-san      | 69deda8f-f15b-46e1-8ee8-bbd23f6617d9 | deleting |      33 |
| ontapnas_10.11.5.186 | ontap-nas      | 4a2130d2-a2a0-4f9d-9928-9ecae99d5693 | online   |     169 |
+----------------------+----------------+--------------------------------------+----------+---------+

then I had attempted to recreate the TBC , and it came back online.

16:05 # tridentctl get backends -n trident
+----------------------+----------------+--------------------------------------+--------+---------+
|         NAME         | STORAGE DRIVER |                 UUID                 | STATE  | VOLUMES |
+----------------------+----------------+--------------------------------------+--------+---------+
| ontapsan_10.11.6.112 | ontap-san      | 69deda8f-f15b-46e1-8ee8-bbd23f6617d9 | online |      33 |
| ontapnas_10.11.5.186 | ontap-nas      | 4a2130d2-a2a0-4f9d-9928-9ecae99d5693 | online |     169 |

Is this correct ?

inland hazel
#

it won't provision a PVC anymore:

  Normal   Provisioning          3s    csi.trident.netapp.io_trident-csi-9896f497-vbstx_94178f97-b18a-4267-8c37-0d741c5a6676  External provisioner is provisioning volume for claim "default/globalbioimaging-pv-claim"
  Normal   ExternalProvisioning  3s    persistentvolume-controller                                                            waiting for a volume to be created, either by external provisioner "csi.trident.netapp.io" or manually created by system administrator
  Normal   ProvisioningFailed    3s    csi.trident.netapp.io                                                                  no available backends for storage class basic-csi-iscsi
  Warning  ProvisioningFailed    3s    csi.trident.netapp.io_trident-csi-9896f497-vbstx_94178f97-b18a-4267-8c37-0d741c5a6676  failed to provision volume with StorageClass "basic-csi-iscsi": rpc error: code = Unknown desc = no available backends for storage class basic-csi-iscsi
hoary cypress
#

You'll need to check to see why your Backend config isn't matching what is in your StorageClass.