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

PVのONTAP ボリュームが削除されないためにPVCが終了しています

Views:
15
Visibility:
Public
Votes:
0
Category:
astra_trident<a>翻訳の場合</a>
Specialty:
snapx
Last Updated:

環境

Kubernetes / OpenShift 向け Trident

問題

Kubernetes / Tridentスナップショットを作成
し、そこから別のポッドに使用されるKubernetes PVCクローンを作成して元のポッドを終了し、PVCを削除しても、Trident内のPV情報は完全に消去されません。

クローン負荷の高いSnapshotで少なくとも2つのエラーが表示されているため、削除に失敗します。
  1. type: 'Warning' reason: 'VolumeFailedDelete' persistentvolume pvc-UUID is still attached to node WORKER_NODE
  2. API status: failed, Reason: Failed to delete volume \"trident_PREFIX_pvc_UUID\" in Vserver \"VSERVER\"because it has one or more clones.\n\nUse the \"volume clone show -parent-vserver VSERVER -parent-volume trident_PREFIX_pvc_UUID\" command to list clones, and either delete or split the clones and retry the operation.\n\nUse \"volume clone split start -vserver \u003cvserver name\u003e -flexclone \u003cclone name\u003e\" to split clones.\nUse \"volume delete -vserver \u003cvserver name\u003e -volume \u003cclone name\u003e\" to delete clones., Code 15894","level":"error","message":"Unable to delete volume from backend."

また、出力にPVCが「Releasedoc|kubectl get pvc -o wide」と表示されます。

 

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.