メインコンテンツまでスキップ

Trident backedが「deleting」状態でスタックし、削除できません

Views:
10
Visibility:
Public
Votes:
0
Category:
astra_trident<a>2009532520</a>
Specialty:
snapx
Last Updated:

環境

  • Astra Trident
  • OpenShift Container Platform(OCP)

問題

Tridentバックエンドは削除中です:

+------------------+----------------+--------------------------------------+----------+---------+
|       NAME       | STORAGE DRIVER |                 UUID                 |  STATE   | VOLUMES |
+------------------+----------------+--------------------------------------+----------+---------+
| ISCSI-Backend   | ontap-san      | 74d7c2af-7140-41d3-b66d-7943477075cd | online   |      27 |
| NFS-Backend    | ontap-nas      | 5e542122-563c-4c86-a34d-f0528be250e5 | deleting |       1 |
+------------------+----------------+--------------------------------------+----------+---------+


バックエンドの状態は「failed」です。

# tridentctl get backend NFS-Backend -oyaml | tail
    zone: ""
  configRef: ""
  name: NFS-Backend
  online: false
  protocol: file
 state: failed
  storage: {}
  volumes:
  - pvc-5e96748f-5ebb-473d-b942-dd78d729469f


対応するボリュームを削除しようとするとエラーが発生します:

# tridentctl  -d delete volume pvc-5e96748f-5ebb-473d-b942-dd78d729469f
Operating mode = tunnel, Trident pod = trident-csi-785fbd5587-78dt4, Namespace = otrident, CLI = oc
Invoking tunneled command: oc exec trident-csi-785fbd5587-78dt4 -n otrident -c trident-main -- tridentctl --debug delete volume pvc-5e96748f-5ebb-473d-b942-dd78d729469f
Operating mode = direct, Server = 127.0.0.1:8000, Autosuport server = 127.0.0.1:8003
Trident URL: http://127.0.0.1:8000/trident/v1
--------------------------------------------------------------------------------
Request Method: DELETE
Request URL: http://127.0.0.1:8000/trident/v1/volume/pvc-5e96748f-5ebb-473d-b942-dd78d729469f
Request headers: map[Content-Type:[application/json]]
Request body:
................................................................................
Error: could not delete volume pvc-5e96748f-5ebb-473d-b942-dd78d729469f: backend NFS-Backend is not Online or Deleting (400 Bad Request)
Response status: 400 Bad Request
Response headers: map[Content-Length:[58] Content-Type:[application/json; charset=UTF-8] Date:[Tue, 18 Apr 2023 10:56:03 GMT]]
Response body: {"error":"backend NFS-Backend is not Online or Deleting"}


バックエンドの更新が次のエラーで失敗します。

# tridentctl update backend NFS-Backend  -f NAS_Trident_Node1.json  -n trident
Error: could not update backend NFS-NPUATS2: problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post https://192.168.0.25/servlets/netapp.servlets.admin.XMLrequest_filer: dial tcp 192.168.0.25:443: connect: connection refused (400 Bad Request)
command terminated with exit code 1

 

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.